Packt+ | Advance your knowledge in tech

You're reading from Software Architect‚àö¬¢‚Äö√á¬®‚Äö√ë¬¢s Handbook Become a successful software architect by implementing effective architecture concepts

Product type Paperback

Published in Aug 2018

Publisher Packt

ISBN-13 9781788624060

Length 594 pages

Edition 1st Edition

Concepts

Software Architecture

Author (1):

Joseph Ingeno

View More author details

Table of Contents (24) Chapters

Title Page

Dedication

Packt Upsell

Contributors

Preface

1. The Meaning of Software Architecture FREE CHAPTER

2. Software Architecture in an Organization

3. Understanding the Domain

4. Software Quality Attributes

5. Designing Software Architectures

6. Software Development Principles and Practices

7. Software Architecture Patterns

8. Architecting Modern Applications

9. Cross-Cutting Concerns

10. Performance Considerations

11. Security Considerations

12. Documenting and Reviewing Software Architectures

13. DevOps and Software Architecture

14. Architecting Legacy Applications

15. The Soft Skills of Software Architects

16. Evolutionary Architecture

17. Becoming a Better Software Architect

1. Other Books You May Enjoy

Leave a review - let other readers know what you think

Index

Cross-cutting concerns for microservices

Providing cross-cutting concerns for microservices requires some additional consideration. In this section, we will take a look at using a microservice chassis and the sidecar pattern to handle some of the difficulties with implementing cross-cutting concerns for microservices.

Leveraging a microservice chassis

In a monolithic application, cross-cutting concerns can be designed and developed once. After their development is complete and they are available for use, they can be leveraged throughout the application.

Microservices are independently deployable, self-contained services. As a result, implementing a cross-cutting concern has to be done repeatedly for each microservice. This can make it prohibitively expensive for an organization to develop microservices when considering the development resources that would be needed. A system may consist of hundreds of microservices, and your team may be creating new ones throughout the life of the application...