Microservices-seminar-exercise PDF

Preview

Summary

SEMINAR TOPIC 4: MICROSERVICES What are the technical challenges that the company is currently facing? Define how to split microservices Growth/scaling up. Slow speed of new feature deployment / Speeding up feature deployment. Setting up the whole microservice ecosystem and bring SWE up to speed wit...

Description

SEMINAR TOPIC 4: MICROSERVICES

1) What are the technical challenges that the company is currently facing? 1. 2. 3. 4.

Define how to split microservices Growth/scaling up. Slow speed of new feature deployment / Speeding up feature deployment. Setting up the whole microservice ecosystem and bring SWE up to speed with microservices tools and technologies. 5. Spikes in activity 6. Single point of failure

2) Which of CoolSocks’s problems can be addressed by shifting to microservice architecture? − − −

Independent scalability (Tech Challenge 2) Quick deployment of new features (Tech Challenge 3) Quicker compile time ()

3) How a microservice architecture can help with 24/7 availability of the CoolSockswebsite? − − −

Using a bulkhead pattern in its design approach to segregate components and reduce dependencies Microservices architecture is usually built for failure and resilient to errors/issues within microservices Introduce zero downtime deployment

4) Draw an architecture diagram outlining the new components in the system and how they are connected. Explain each component with few words. COMPONENT LIST -

Catalogue Wish list Reviews Cart Payment/ billing Recommendation Incentive component to reward points based on reviews Customer service

5) The recommendation system uses a third-party API that often returns an error. How will you ensure that an error in the recommendation system will not bring down the whole website? By designing the microservices architecture in a way that is resilient to errors. This is achieved by following common design patterns such as bulkhead. 6) What design patterns can be used to make the system easy to deploy? Blue-Green Deployment Pattern. 7) What are the risks of moving to microservice architecture? Be specific and give examples.

-

Not having SWE trained on this topic, therefore unable to design the architecture well enough and fix issues when they arise. More services interacting therefore increase in failure points

8) How will you split the teams in the company? Each team will take care of one or more microservices. The team will handle everything that the microservice comprises, therefore in each team there should be a specialist for every aspect of the microservice, such as front-end, back-end, database expert, etc Consequently, there could be a team for the “Customer service” microservice, another for the “Cart & payment and billing” microservices, etc.

9) What are the challenges in implementing the solution? Splitting the tasks and designing microservices Setting up CI/CD pipelines Costly to change from one architecture to another Restructuring teams

1709869@brunel....