filmov
tv
What are Microservices? - Microservices Explained - Learn Microservice Architecture
Показать описание
Microservice Architecture is an architectural style in which we can structure an application as a collection of services.
The Microservice Architecture has become hugely popular in recent years. Experts predict that all New Apps Will Feature Microservice Architectures that improve the ability to design, debug, update, and leverage third-party code. Microservice architecture will continue to help businesses reduce downtime, optimize resources, and decrease infrastructure costs.
Topics covered in this video:
1. What is a Microservice Architecture
2. Traditional Monolithic Architecture
3. Microservice and Monolithic Comparison
4. Microservice Pros and Cons
5. Introduction to Docker and Container
The Microservices are:
- Independently deployable. Each microservices can be deployed autonomously and independently.
- Organized around business capabilities
- Highly maintainable and testable
- Loosely coupled
- Owned by a small team
- The microservices can also have separate databases
- The microservices can communicate each other. We can implement APIs for service-to-service communication
- They can have different technologies
- Can be developed using different languages
Monolithic Architecture:
A monolithic architecture is the traditional unified model for the design of a software program.
It is like a big container, wherein all the software components of an app are assembled and tightly coupled. That means each component fully depends on each other.
Pros of Microservices (Pros of Microservice Architecture):
- The biggest pro of microservices are that it can be developed, maintained and deployed independently.
- Microservices can be scaled easily as you can do it separately whenever its necessary.
- It is easier to maintain and debug a lightweight microservice than a complex application.
- If one service got stopped due to some error, still the other services continue to work as they are independent services and loosely coupled. So, failover of one microservice does not affect the working of other microservices.
- Developers have the flexibility to experiment with different technologies while creating various services. There are lesser technology dependencies between the modules. Rolling back to the previous iterations is less complicated.
- As one module has one responsibility encapsulated within, it becomes easier to understand the code base for that module.
Cons of Microservices (Cons of Microservice Architecture):
- Splitting an application into multiple smaller modules increases the communication overhead. Developers must be cautious while handling requests.
- With an increasing number of microservices, the resources needed to implement them increases as well.
- Each service needs to be launched and tested individually first. Then the application as a whole needs to be tested again, once all the services are launched.
- Microservices architecture is a good option for bigger applications. But, for smaller apps, it will probably be more time consuming and challenging to implement.
- The deployment could be a complicated and challenging procedure. It would need coordination between multiple services during deployment.
What is Docker?
Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly.
Docker allows you containerize your microservices and simplify the delivery and management of those microservices. Containerization provides individual microservices with their own isolated workload environments, making them independently deployable and scalable.
A container is a standard unit of software that packages up code and all its dependencies, so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.
#CodingDroplets #Microservices
The Microservice Architecture has become hugely popular in recent years. Experts predict that all New Apps Will Feature Microservice Architectures that improve the ability to design, debug, update, and leverage third-party code. Microservice architecture will continue to help businesses reduce downtime, optimize resources, and decrease infrastructure costs.
Topics covered in this video:
1. What is a Microservice Architecture
2. Traditional Monolithic Architecture
3. Microservice and Monolithic Comparison
4. Microservice Pros and Cons
5. Introduction to Docker and Container
The Microservices are:
- Independently deployable. Each microservices can be deployed autonomously and independently.
- Organized around business capabilities
- Highly maintainable and testable
- Loosely coupled
- Owned by a small team
- The microservices can also have separate databases
- The microservices can communicate each other. We can implement APIs for service-to-service communication
- They can have different technologies
- Can be developed using different languages
Monolithic Architecture:
A monolithic architecture is the traditional unified model for the design of a software program.
It is like a big container, wherein all the software components of an app are assembled and tightly coupled. That means each component fully depends on each other.
Pros of Microservices (Pros of Microservice Architecture):
- The biggest pro of microservices are that it can be developed, maintained and deployed independently.
- Microservices can be scaled easily as you can do it separately whenever its necessary.
- It is easier to maintain and debug a lightweight microservice than a complex application.
- If one service got stopped due to some error, still the other services continue to work as they are independent services and loosely coupled. So, failover of one microservice does not affect the working of other microservices.
- Developers have the flexibility to experiment with different technologies while creating various services. There are lesser technology dependencies between the modules. Rolling back to the previous iterations is less complicated.
- As one module has one responsibility encapsulated within, it becomes easier to understand the code base for that module.
Cons of Microservices (Cons of Microservice Architecture):
- Splitting an application into multiple smaller modules increases the communication overhead. Developers must be cautious while handling requests.
- With an increasing number of microservices, the resources needed to implement them increases as well.
- Each service needs to be launched and tested individually first. Then the application as a whole needs to be tested again, once all the services are launched.
- Microservices architecture is a good option for bigger applications. But, for smaller apps, it will probably be more time consuming and challenging to implement.
- The deployment could be a complicated and challenging procedure. It would need coordination between multiple services during deployment.
What is Docker?
Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly.
Docker allows you containerize your microservices and simplify the delivery and management of those microservices. Containerization provides individual microservices with their own isolated workload environments, making them independently deployable and scalable.
A container is a standard unit of software that packages up code and all its dependencies, so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.
#CodingDroplets #Microservices
Комментарии