Microservice…….the new kid around the block

Errol Fernandes
2 min readFeb 21, 2019

--

Application architecture has gone through various changing trends in the dynamic technological era. To sum up in simple words initially applications were developed with the monolithic architecture but now with the advent of various cloud providers in market and thanks to the heavy competition between them we have services using which we can develop applications in a microservice based architecture which helps in handling traffic spikes and also brings down the infrastructure expenditure.

If you plan to have a near-zero cost architecture for your application then building your technology stack using lambda or google cloud functions should be the right approach. It’s an event-based approach. A more reactive way and less coupled way to integrate systems. Lambda does provide a cost-efficient solution but if you have a process that is gonna take a long time then you may need to build your microservice on a container platform. Depending on the complexity and processing speed of the business logic you need to define the underlying platform on which your microservice will run. It could range from the lightweight google functions to the heavyweight containers.

Microservices architecture may be a very delightful and cost-efficient solution but when you have a complex architecture, things can easily turn into chaos. One problem with using this approach is deciding when it makes sense to use it. Therefore you need to define your problem statement and also have a clear roadmap defined and determine whether the microservices strategy fits your requirement goals. When developing the first version of an application, you often do not have the problems that this approach solves. Moreover, using an elaborate, distributed architecture will slow down development. This can be a major problem for startups whose biggest challenge is often how to rapidly evolve the business model and the application. Therefore the teams working on individual microservices need to be defined well and the microservices flow needs to be kept in control. As said by a great man “ With great powers come great responsibilities”.

--

--

Errol Fernandes

AWS Certified Architect, Google Cloud Certified Professional Cloud Architect