Business Use Case For Microservices

Microservices are potentially too micro because they aren t respecting the boundaries of real business contexts.

Business use case for microservices. Decomposition by resources in this case microservice covers all operations of a specific field. What is the use of microservices. Key benefits of microservices.

Microservices examples and business use cases. Use duplication libraries duplication with managed copy paste and expose as microservices depending on the use case and be open to change if it doesn t work down the line. Smaller more productive teams reduced risk of change faster software delivery lower risk to introduce new technologies lower risks and costs of replacing.

Instead of focusing on size we ought to focus on proper boundaries which is a topic for another day. A microservices based architecture offers a lot of benefits in theory but it s difficult to make it work in practice. Here s your rule of thumb.

Should you use a microservices architecture. Easier to use for business logic that involves read operations. Each microservice must encapsulate a business capability.

A function that takes an image as input and converts it into different file types is a better use case for microservices as it s a more encapsulating service. A business case for microservices key takeaways microservices is an approach of breaking up software into services that are small and do one thing well. The litmus test must cover all the microservices benefits we discussed earlier in this chapter.

Martin fowler talks about complexity vs productivity so in theory if you know in advance how complex your project is going to be maybe you have a valid microservices use case. You should do what makes sense for your business. Decomposition by use case i e microservices handle specific actions.