UrbanPiper offers a platform for end-to-end automation of critical workflows in the online food delivery ecosystem.Restaurants can effectively manage their storefronts on aggregator marketplaces as well as deploy their self-branded websites/apps to build a sustainable online business.

LoReMo was a product meant to help forge a relationship based on data, transparency and engagement between merchants and consumers. The engagement and loyalty sector has for decades relied upon plastic cards based solution—iterating over and over to make it somewhat more efficient. However, with the advent of smartphones, there existed a strong opportunity for having a solution which makes use of the vast computing potential of smartphones and provide a big leap in this sector. The solution stack was primarily developed keeping in mind high-availability, high-concurrency and significant user loads.§ At the server side, it was important to keep the communication agnostic of the server or the client technology. I evaluated and decided to make use of a REST based services platform and rely on JSON as interchangeable data format.§ Implemented a clustered server architecture making use of elementary round-robin load balancing to take care of fail-over and high user loads. On a quad core, 4 Gig linux server we were able to cater to nearly 300 concurrent users over a sustained period of time, without any significant degradation in performance. For a more realistic and reasonable load of 100 users, the single server could handle without any error for almost all its running time.§ Put in place a distributed caching framework — Hazelcast — which took care of providing a high availability read cache for our database operations. On an average, the caching framework provided us request time upsides of 4x-5x.§ Made use of master-slave replicating MySQL servers to provide further gains in request times. All write requests were directed to one server, while reads were made from the other. This solution also backed up as a fail-over option, in case one of the servers acted up.(dang alert — approaching word limit. For further reading — http://anirvan-majumdar.github.io/blog/2013/07/26/slowing-things-down/)

I got to work on a lot of enterprisey stuff here. Mostly the work was related to taking a suite of standalone, desktop applications and provide a cloud based offering relying extensively on web-services.As a Team Leader, I was responsible for putting together a team, architecting a solution within the constraints of legacy applications and putting together the checks-and-balances for a predictable and reliable development cycle.§ Built a prototype with the capability of communicating across different web-services and massaging formats to provide interoperability. § Implemented the first version of the application using a Enterprise Service Bus — Apache Service Mix, which relied on the capabilities of ActiveMQ, Apache Karaf and Camel to provide a whole world of interoperability, message queueing, routing capabilities.§ Learned and mentored the team on a technology — OSGi — which was still in its early stages of development and highly volatile. § Recruited the team to work alongside on the project.§ Developed an in-house solution within a short period of time (during notice period) to alleviate the manual process of keeping track of developer work hours through Excel worksheets.

My first step outside the comfortable confines of a big organisation - and into the figurative jungle of tech startups.>> Learnt to appreciate and dedicate myself to the true ethics and philosophy of being a complete programmer.>> Embraced the generality of understanding and working with unheard of frameworks related to mapping and GIS, Grinder for load and performance testing, Rule engines, ad servers, PHP, json, ORM's, linux, bash, etc.>> Understood the true meaning and relevance of accountability, owning my own product, and being the last point of responsibility for everything related to the work I do.>> Took up challenges to infuse things that I was passionate about into a startup ecosystem - knowledge sharing through a personalised Wiki, overhauling product design aesthetics, testing products for quality and super-scaling ( > 10 million users) issues.