concept monolithic application in category microservice

This is an excerpt from Manning's book Microservices Security in Action.

This is an excerpt from Manning's book Microservices in Action.
In a monolithic application, you try to design for these properties at a class, module, or library level. In a microservice application, you aim instead to attain these properties at the level of independently deployable units of functionality. A single microservice should be highly cohesive: it should be responsible for some single capability within an application. Likewise, the less that each service knows about the inner workings of other services, the easier it is to make changes to one service — or capability — without forcing changes to others.
With a monolithic application, your primary deliverable is a single application. That application is split horizontally into different technical layers — in a typical three-tier application, they’d be data, logic, and presentation (figure 3.1) — and vertically into different business domains. Patterns like MVC and frameworks like Rails and Django reflect the three-tier model. Each tier provides services to the tier above: the data tier provides persistent state; the logic tier executes useful work; and the presentation layer presents the results back to the end user.