Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Cloud-Native Microservices with Jakarta EE

You're reading from   Hands-On Cloud-Native Microservices with Jakarta EE Build scalable and reactive microservices with Docker, Kubernetes, and OpenShift

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781788837866
Length 352 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Luigi Fugaro Luigi Fugaro
Author Profile Icon Luigi Fugaro
Luigi Fugaro
Mauro Vocale Mauro Vocale
Author Profile Icon Mauro Vocale
Mauro Vocale
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Jakarta EE - the New Open Source Life of Java EE 2. Microservices and Reactive Architecture FREE CHAPTER 3. Cloud-Native Applications 4. Building Microservices Using Thorntail 5. Eclipse MicroProfile and Transactions - Narayana LRA 6. Linux Containers 7. Platform as a Service 8. Microservices Patterns 9. Deployment 10. Monitoring 11. Building Microservices Using Spring Boot 2 12. Building Microservices Using Vert.X 13. Other Books You May Enjoy

Decomposition

Decomposition isn't really the best of words—it recalls something going bad. However, in this context, it means to split apart a service, such as our football manager application; that is, splitting it into different microservices and decoupling components that follow the Single Responsibility Principle (SRP). The SRP relies on the fact that one component does one and one thing only, and that it does very well. The following diagram gives us an idea about decomposition:

In our example, the overall application could have been designed and deployed as a monolith, where we group all of the pieces together. Of course, it would have worked well, but with a lot of drawbacks (flexibility, scalability, failure, elasticity, and so on).

How do you decompose an application...

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 $19.99/month. Cancel anytime
Banner background image