- About This E-Book
- Title Page
- Copyright Page
- Dedication
- Contents at a Glance
- Contents
- Preface
- Acknowledgments
- About the Author
- Part I: Motivation and Basics
- Chapter 1. Preliminaries
- Chapter 2. Microservice Scenarios
- 2.1 Modernizing an E-Commerce Legacy Application
- Scenario
- Reasons to Use Microservices
- Slow Continuous Delivery Pipeline
- Parallel Work Is Complicated
- Bottleneck During Testing
- Approach
- Challenges
- Entire Migration Lengthy
- Testing Remains a Challenge
- Current Status of Migration
- Creating Teams
- Advantages
- Conclusion
- Rapid and Independent Development of New Features
- Influence on the Organization
- Amazon Has Been Doing It for a Long Time
- 2.2 Developing a New Signaling System
- 2.3 Conclusion
- 2.1 Modernizing an E-Commerce Legacy Application
- Part II: Microservices: What, Why, and Why Not?
- Chapter 3. What Are Microservices?
- Chapter 4. Reasons for Using Microservices
- Chapter 5. Challenges
- Chapter 6. Microservices and SOA
- Part III: Implementing Microservices
- Chapter 7. Architecture of Microservice-Based Systems
- 7.1 Domain Architecture
- 7.2 Architecture Management
- 7.3 Techniques to Adjust the Architecture
- 7.4 Growing Microservice-Based Systems
- 7.5 Don’t Miss the Exit Point or How to Avoid the Erosion of a Microservice (Lars Gentsch)
- 7.6 Microservices and Legacy Applications
- 7.7 Hidden Dependencies (Oliver Wehrens)
- 7.8 Event-Driven Architecture
- 7.9 Technical Architecture
- 7.10 Configuration and Coordination
- 7.11 Service Discovery
- 7.12 Load Balancing
- 7.13 Scalability
- 7.14 Security
- 7.15 Documentation and Metadata
- 7.16 Conclusion
- Chapter 8. Integration and Communication
- Chapter 9. Architecture of Individual Microservices
- Chapter 10. Testing Microservices and Microservice-Based Systems
- Chapter 11. Operations and Continuous Delivery of Microservices
- Chapter 12. Organizational Effects of a Microservices-Based Architecture
- 12.1 Organizational Benefits of Microservices
- 12.2 An Alternative Approach to Conway’s Law
- 12.3 Micro and Macro Architecture
- 12.4 Technical Leadership
- 12.5 DevOps
- 12.6 When Microservices Meet Classical IT Organizations (Alexander Heusingfeld)
- 12.7 Interface to the Customer
- 12.8 Reusable Code
- 12.9 Microservices without Changing the Organization?
- 12.10 Conclusion
- Chapter 7. Architecture of Microservice-Based Systems
- Part IV: Technologies
- Chapter 13. Example of a Microservices-Based Architecture
- 13.1 Domain Architecture
- 13.2 Basic Technologies
- 13.3 Build
- 13.4 Deployment Using Docker
- 13.5 Vagrant
- 13.6 Docker Machine
- 13.7 Docker Compose
- 13.8 Service Discovery
- 13.9 Communication
- 13.10 Resilience
- 13.11 Load Balancing
- 13.12 Integrating Other Technologies
- 13.13 Tests
- 13.14 Experiences with JVM-Based Microservices in the Amazon Cloud (Sascha Möllering)
- 13.15 Conclusion
- Chapter 14. Technologies for Nanoservices
- Chapter 15. Getting Started with Microservices
- Chapter 13. Example of a Microservices-Based Architecture
- Index
- Code Snippets
Microservices
Flexible Software Architecture
Eberhard Wolff
Boston • Columbus • Indianapolis • New York • San Francisco
Amsterdam • Cape Town • Dubai • London • Madrid • Milan
Munich • Paris • Montreal • Toronto • Delhi • Mexico City
São Paulo • Sydney • Hong Kong • Seoul • Singapore • Taipei • Tokyo
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.