µServices is not something new, it has been around for many years. Its recent rise is owing to its popularity and visibility. Before µServices became popular, there was primarily monolithic architecture that was being used for developing on premise and cloud applications.

Monolithic architecture allows the development of different components such as presentation, application logic, business logic, and data access objects (DAO), and then you either bundle them together in enterprise archive (EAR)/web archive (WAR), or store them in a single directory hierarchy (for example, Rails, NodeJS, and so on).

Many famous applications such as Netflix have been developed using µServices architecture. Moreover, eBay, Amazon, and Groupon have evolved from monolithic architecture to a µServices architecture.

Now, that you have had an insight into the background and history of µServices, let's discuss the limitations of a traditional approach, namely monolithic app development, and compare how µServices would address them.