filmov
tv
Microservices Interview Questions and Answers for experienced and fresher | Most Asked | Code Decode
![preview_player](https://i.ytimg.com/vi/9x_6VLk3GtY/maxresdefault.jpg)
Показать описание
In this video of code decode we have covered most asked microservices Interview questions and answers. Covered 3 W's (Why What When & H - How)We have covered all the basic microservices interview questions along with their answers.
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
Course Description Video :
What are Microservices?
Microservices is an architecture where the application is exposed as loosely coupled services that can be independently developed, deployed, and maintained. Each service exposed is referred to as Microservice. Each service performs a unique function.
Speciality of this architecture is that polyglot architecture is supported. For example, if a team is working on one of the microservice using Java, Spring Boot, and MySQL, another team can work on another microservice using Python, Node JS, and NoSQL.
Different microservices can use a different version of the same programming language.
Different microservices can use different programming languages.
Different microservices can use different architectures as well.
Q)Why Microservices?
In the case of monolith applications, there are several problems like
Same code base for presentation, business layer, and data access layer. Application is deployed as a single unit.
Complex to maintain and scalability is an issue.
Microservice solves the above problems.
Microservices are ideal when a monolith or a legacy application needs to be modernized.
For new software development, if the key business drivers are to reduce time to market, scalable better software, lower costs, faster development, or cloud-native development, microservices are ideal.
Each service is independent and gives the flexibility to choose the programming language, database, and/or architecture.
Distinct services can be developed, deployed, and maintained independently.
Q) What are the pros and cons of Microservice Architecture?
Pros of Microservice Architecture
1) Freedom to use different technologies
2) Each microservices focuses on single capability
3) Supports individual deployable units
4) Allow frequent software releases
5) Ensures security of each service
6) Multiple services are parallelly developed and deployed
Cons of Microservice Architecture
1) Management of a large number of services is difficult.
2) Communication between microservices is complex.
3) Increased efforts for configuration and other operations
4) Difficult to maintain transaction safety and data boundaries
5) Due to the decentralized nature of microservices, more microservices will mean more resources hence high Investment
6) Debugging of problems is harder unless the right instrumentation is followed during design and development.
7) Microservices will need a large team size with the right mix of experience in design, development, automation, deployments, tools, and testing.
Q) When to use microservices?
Reduce time to market,
Scalable better software,
Lower costs,
Faster development,
Cloud-native development
It makes sense to adopt a microservices architecture, if the team size is big enough as each service will require its team to develop, deploy and manage.
Timeframe and skills of team members are a constraint.
If fast results are required,
choose microservices architecture only if the team also has experience in microservices.
Do not use this architecture for simple application which can be managed by monolithic application .
So you use ask yourself first do we really need microservice architecture
Microservice Interview Questions and Answers part -2
Also if you want to learn microservices from basic you can find all the video in below playlist
Subscriber and Follow Code Decode
#codedecode #microservicesinterviewquestions #microservices
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
Course Description Video :
What are Microservices?
Microservices is an architecture where the application is exposed as loosely coupled services that can be independently developed, deployed, and maintained. Each service exposed is referred to as Microservice. Each service performs a unique function.
Speciality of this architecture is that polyglot architecture is supported. For example, if a team is working on one of the microservice using Java, Spring Boot, and MySQL, another team can work on another microservice using Python, Node JS, and NoSQL.
Different microservices can use a different version of the same programming language.
Different microservices can use different programming languages.
Different microservices can use different architectures as well.
Q)Why Microservices?
In the case of monolith applications, there are several problems like
Same code base for presentation, business layer, and data access layer. Application is deployed as a single unit.
Complex to maintain and scalability is an issue.
Microservice solves the above problems.
Microservices are ideal when a monolith or a legacy application needs to be modernized.
For new software development, if the key business drivers are to reduce time to market, scalable better software, lower costs, faster development, or cloud-native development, microservices are ideal.
Each service is independent and gives the flexibility to choose the programming language, database, and/or architecture.
Distinct services can be developed, deployed, and maintained independently.
Q) What are the pros and cons of Microservice Architecture?
Pros of Microservice Architecture
1) Freedom to use different technologies
2) Each microservices focuses on single capability
3) Supports individual deployable units
4) Allow frequent software releases
5) Ensures security of each service
6) Multiple services are parallelly developed and deployed
Cons of Microservice Architecture
1) Management of a large number of services is difficult.
2) Communication between microservices is complex.
3) Increased efforts for configuration and other operations
4) Difficult to maintain transaction safety and data boundaries
5) Due to the decentralized nature of microservices, more microservices will mean more resources hence high Investment
6) Debugging of problems is harder unless the right instrumentation is followed during design and development.
7) Microservices will need a large team size with the right mix of experience in design, development, automation, deployments, tools, and testing.
Q) When to use microservices?
Reduce time to market,
Scalable better software,
Lower costs,
Faster development,
Cloud-native development
It makes sense to adopt a microservices architecture, if the team size is big enough as each service will require its team to develop, deploy and manage.
Timeframe and skills of team members are a constraint.
If fast results are required,
choose microservices architecture only if the team also has experience in microservices.
Do not use this architecture for simple application which can be managed by monolithic application .
So you use ask yourself first do we really need microservice architecture
Microservice Interview Questions and Answers part -2
Also if you want to learn microservices from basic you can find all the video in below playlist
Subscriber and Follow Code Decode
#codedecode #microservicesinterviewquestions #microservices
Комментарии