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
Java EE 8 Design Patterns and Best Practices

You're reading from   Java EE 8 Design Patterns and Best Practices Build enterprise-ready scalable applications with architectural design patterns

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781788830621
Length 314 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Rhuan Rocha Rhuan Rocha
Author Profile Icon Rhuan Rocha
Rhuan Rocha
Paulo Alberto Simoes Paulo Alberto Simoes
Author Profile Icon Paulo Alberto Simoes
Paulo Alberto Simoes
Joao Carlos Purificação Joao Carlos Purificação
Author Profile Icon Joao Carlos Purificação
Joao Carlos Purificação
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Introduction to Design Patterns FREE CHAPTER 2. Presentation Patterns 3. Business Patterns 4. Integration Patterns 5. Aspect-Oriented Programming and Design Patterns 6. Reactive Patterns 7. Microservice Patterns 8. Cloud-Native Application Patterns 9. Security Patterns 10. Deployment Patterns 11. Operational Patterns 12. MicroProfile 13. Other Books You May Enjoy

Advantages and drawbacks of a microservices-based application


Like any other technology, there are advantages and disadvantages in using microservices-based architecture. Several problems may appear during the implementation of microservices, but the advantages can overcome the complexity encountered during development. 

The following are the advantages of the microservices architecture:

  • Small multitask team.
  • Services can be written in different languages. This is a positive point because depending on the service, a specific language may provide more tools than another in obtaining the functionality served by the service.
  • The deployment is faster and integration is performed more automatically. Changes of requirements mean only the deployment of the related microservice.
  • The latest libraries, frameworks, and technologies can be quickly used.
  • Greater fault tolerance.
  • The microservice is related to the product and not to the project. The developer has more freedom and thus can develop the service...
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