Monolithic Vs Microservice
Most of the server side applications currently in
existence follow this architecture. All the business functionalities are
coupled into a single big block of deployable component. It can be .jar , .war
or , .ear.
References:
1) www.google.com
2) https://en.wikipedia.org/
Pros:
·
Simplicity, for small codebases
·
Faster early development speed
·
Easy testing
Cons:
·
Not ideal for growing codebases
·
Slower iterations in the long term
·
Harder to innovate
·
Steep code learning curve
·
Slower velocity getting into prodcution
·
Single point of failure
·
Deploy everything at once or nothing at all
Microservices is a new software architecture. It is based on
web services. But it can be any service implemented as an independent feature
that has its own database and can be deployed independently. In a Web service
we just create a service for an application that can be accessed by web
protocols. Microservices are generally implemented in REST over HTTP protocol.
Webservices can be implemented in REST, SOAP etc. Many new companies like
Netflix, Amazon, Walmart etc use Microservices in their enterprise level
software.
The big block of code in the monolithic architecture
is broken down into applications with bound business contexts.
Pros:
- · Better agility in the long-term
- · Small team and easy to learn
- · Efficient scaling
- · Resilient
Cons:
- · More moving parts
- · Complex infrastructure requirements
1) www.google.com
2) https://en.wikipedia.org/

