Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building Microservices with Spring

You're reading from   Building Microservices with Spring Master design patterns of the Spring framework to build smart, efficient microservices

Arrow left icon
Product type Course
Published in Dec 2018
Publisher Packt
ISBN-13 9781789955644
Length 502 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Rajesh R V Rajesh R V
Author Profile Icon Rajesh R V
Rajesh R V
Dinesh Rajput Dinesh Rajput
Author Profile Icon Dinesh Rajput
Dinesh Rajput
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

Title Page
Copyright
About Packt
Contributors
Preface
1. Getting Started with Spring Framework 5.0 and Design Patterns FREE CHAPTER 2. Overview of GOF Design Patterns - Core Design Patterns 3. Wiring Beans using the Dependency Injection Pattern 4. Spring Aspect Oriented Programming with Proxy and Decorator pattern 5. Accessing a Database with Spring and JDBC Template Patterns 6. Improving Application Performance Using Caching Patterns 7. Implementing Reactive Design Patterns 8. Implementing Concurrency Patterns 9. Demystifying Microservices 10. Related Architecture Styles and Use Cases 11. Building Microservices with Spring Boot 12. Scale Microservices with Spring Cloud Components 13. Logging and Monitoring Microservices 14. Containerizing Microservices with Docker 15. Scaling Dockerized Microservices with Mesos and Marathon 1. Other Books You May Enjoy Index

Microservice use cases


Microservice is not a silver bullet, and it will not solve all the architectural challenges of today's world. There is no hard and fast rule, or a rigid guideline on when to use microservices.

Microservices may not fit in each and every use case. The success of microservices largely depends on the selection of use cases. The first and the foremost activity is to do a litmus test of the use case against the microservices benefits. The litmus test must cover all microservices benefits we had discussed earlier in this chapter. For a given use case, if there are no quantifiable benefits, or if the cost is outweighing the benefits, then the use case may not be the right choice for microservices.

Let's discuss some commonly used scenarios that are suitable candidates for a microservice architecture:

  • Migrating a monolithic application due to improvements required in scalability, manageability, agility, or speed of delivery. Another similar scenario is rewriting an end-of-life...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime