Monolithic:
1. What are they?
Architecture where everything is in one place
o E.g., 1 programming language such as Java, compile application as 1 unit, and deploy
as 1 unit
o Standard practice for building monolithic architecture is building in layers:
▪ Data layer – database
▪ Access layer – classes and libraries that access database
▪ Business logic – classes that have the logic of application, basic
functionalities
▪ User interface layer
2. Why are they used; How are they used; When are they used;
Monolithic architecture is commonly used for developing small to medium-sized applications, where
the codebase is relatively small, and the development team is also small. This makes it easier to
develop and deploy the application as they do not require complex configuration or management of
separate components. E.g., web applications and desktop applications.
Monolithic architectures are typically used in the development of software applications where the
entire application is built as a single, self-contained unit.
3. Advantages and disadvantages;
Advantages of Monolithic Architecture:
• Easy
• Simple
Disadvantages of Monolithic Architecture:
• Must replicate whole application
• Scalability – the more scalability there is, the better it is, it allows for more traffic without
sacrificing performance.
• If one part goes down in the system, the whole thing goes down
Microservices:
1. What are they?
Microservices = Independent Deployment Units
each service is developed and deployed independently, which allows for greater flexibility and
scalability
• Independent – when building a component, it should not be dependent or too coupled with
other features on system. If this goes down, it shouldn’t affect other features
• Deployment – need to be able to deploy services independently, service by service and not
as a whole
• A microservice is a software architectural style focused on decomposing applications into
single-function modules with well-defined interfaces which are independently deployed and
operated by small teams who own the entire lifecycle of the service.
, • Microservices accelerate delivery by minimizing communication and coordination between
people while reducing the scope and risk of change.
2. Why are they used; How are they used; When are they used;
Why - They are used because of scalability, resilience and flexibility.
How – they are used in complex applications that require high scalability and availability.
When – applications are large, complex and require high scalability, resilience and agility.
3. Advantages and disadvantages;
Monolith vs microservices
Monolithic Microservice
• Used for smaller applications • Used for bigger applications
• Has single database • Can have multiple databases
• Has single programming language • Can have multiple programming
• Has single deployment languages
• Harder to scale for large applications – • Can have individual deployment units
as it uses more resources • Easier to scale applications as they are
• Easier to scale for smaller applications split into different components – allows
• Can't work on multiple features at the resource management accordingly
same time and takes longer to deploy • Can work on features individually and
• Easier to troubleshoot as only one deploy much quicker
programming language • Harder to troubleshoot because of
multiple programming languages
1. What are they?
Architecture where everything is in one place
o E.g., 1 programming language such as Java, compile application as 1 unit, and deploy
as 1 unit
o Standard practice for building monolithic architecture is building in layers:
▪ Data layer – database
▪ Access layer – classes and libraries that access database
▪ Business logic – classes that have the logic of application, basic
functionalities
▪ User interface layer
2. Why are they used; How are they used; When are they used;
Monolithic architecture is commonly used for developing small to medium-sized applications, where
the codebase is relatively small, and the development team is also small. This makes it easier to
develop and deploy the application as they do not require complex configuration or management of
separate components. E.g., web applications and desktop applications.
Monolithic architectures are typically used in the development of software applications where the
entire application is built as a single, self-contained unit.
3. Advantages and disadvantages;
Advantages of Monolithic Architecture:
• Easy
• Simple
Disadvantages of Monolithic Architecture:
• Must replicate whole application
• Scalability – the more scalability there is, the better it is, it allows for more traffic without
sacrificing performance.
• If one part goes down in the system, the whole thing goes down
Microservices:
1. What are they?
Microservices = Independent Deployment Units
each service is developed and deployed independently, which allows for greater flexibility and
scalability
• Independent – when building a component, it should not be dependent or too coupled with
other features on system. If this goes down, it shouldn’t affect other features
• Deployment – need to be able to deploy services independently, service by service and not
as a whole
• A microservice is a software architectural style focused on decomposing applications into
single-function modules with well-defined interfaces which are independently deployed and
operated by small teams who own the entire lifecycle of the service.
, • Microservices accelerate delivery by minimizing communication and coordination between
people while reducing the scope and risk of change.
2. Why are they used; How are they used; When are they used;
Why - They are used because of scalability, resilience and flexibility.
How – they are used in complex applications that require high scalability and availability.
When – applications are large, complex and require high scalability, resilience and agility.
3. Advantages and disadvantages;
Monolith vs microservices
Monolithic Microservice
• Used for smaller applications • Used for bigger applications
• Has single database • Can have multiple databases
• Has single programming language • Can have multiple programming
• Has single deployment languages
• Harder to scale for large applications – • Can have individual deployment units
as it uses more resources • Easier to scale applications as they are
• Easier to scale for smaller applications split into different components – allows
• Can't work on multiple features at the resource management accordingly
same time and takes longer to deploy • Can work on features individually and
• Easier to troubleshoot as only one deploy much quicker
programming language • Harder to troubleshoot because of
multiple programming languages
