Microservices
Microservices
Flexible Software Architectures
About the Book
A Microservices Architecture divides software systems in many small services that can be deployed independently. Every team is working on its own Microservices and is thereby decoupled from other teams. That allows to easily scale agile processes. The modularization into Microservices protects the system against the decay of the architecture. So systems based on Microservice stay maintainable in the long term. In addition, legacy systems can be migrated into Microservices without changing the legacy code. And Continuous Delivery is easier to implement in Microservice systems.
Eberhard Wolff's book offers a comprehensive introduction to Microservices. It covers:
- Advantages and disadvantages of the Microservice approach
- Microservices vs. SOA (Service-oriented Architecture)
- The architecture of Microservice-based systems
- The architecture of individual Microservices
- Impact on project organization, operation, testing and deployment
- Nanoservices
The book explains technology-neutral concepts and architectures that can be implemented with various technologies. As an example a concrete Java technology stack is shown with Spring Boot, the Netflix stack and Spring Cloud.
On the basis of many examples and concrete scenarios you will learn how Microservices can be used as effective as possible. You'll also get suggestions to deepen what you have learned through your own experiments.
Audience
- Software Developers
- Software Architects
- Technical Project Manager
- Ops and DevOps engineers
Status
The book is translated from German. See http://microservices-buch.de for the German version. The sample contains chapter 1, 2 and parts of 4 which give a good introduction into the book.
Website
The book has a website at http://microservices-book.com
About the Author
Reader Testimonials
Matthias Fritschi
Surprisingly, the best book on Microservices is in German: "Microservices" by @ewolff (about the original German version) http://bit.ly/22HatRp
Peter Storch
For IT topics I usually prefer English literature, but I really recommend "Continuous Delivery" and "Microservices" by @ewolff. (about the original German version) http://bit.ly/1kFWRn2
Table of Contents
-
-
1 Preface
- 1.1 Overview of Microservice
- 1.2 Why Microservices
- Part I: Motivation and Basics
-
2 Introduction
- 2.1 Overview of the Book
- 2.2 For Whom is the Book Meant?
- 2.3 Chapter Overview
- 2.4 Essays
- 2.5 Paths Through the Book
- 2.6 Acknowledgment
-
3 Microservice Scenarios
- 3.1 Modernizing an E-Commerce Legacy Application
- 3.2 Developing a New Signaling System
- 3.3 Conclusion
- Part II: Microservices: What, Why and Why Not?
-
4 What are Microservices?
- 4.1 Size of a Microservice
- 4.2 Conway’s Law
- 4.3 Domain-Driven Design and Bounded Context
- Why You Should Avoid a Canonical Data Model (Stefan Tilkov)
- 4.4 Microservices with UI?
- 4.5 Conclusion
-
5 Reasons for Microservices
- 5.1 Technical Benefits
- 5.2 Organizational Benefits
- 5.3 Benefits from a Business Perspective
- 5.4 Conclusion
-
6 Challenges
- 6.1 Technical Challenges
- 6.2 Architecture
- 6.3 Infrastructure and Operations
- 6.4 Conclusion
-
7 Microservices and SOA
- 7.1 What is SOA?
- 7.2 Differences Between SOA and Microservices
- 7.3 Conclusion
- Part III: Implementing Microservices
-
8 Architecture of Microservice based Systems
- 8.1 Domain Architecture
- 8.2 Architecture Management
- 8.3 Techniques to Adjust the Architecture
- 8.4 Growing Microservice based Systems
- Don’t Miss the Exit Point or How to Avoid the Erosion of a Microservice (Lars Gentsch)
- 8.5 Microservices and Legacy Applications
- Hidden Dependencies (Oliver Wehrens)
- 8.6 Event-driven Architecture
- 8.7 Technical Architecture
- 8.8 Configuration and Coordination
- 8.9 Service Discovery
- 8.10 Load Balancing
- 8.11 Scalability
- 8.12 Security
- 8.13 Documentation and Metadata
- 8.14 Conclusion
-
9 Integration and Communication
- 9.1 Web and UI
- 9.2 REST
- 9.3 SOAP and RPC
- 9.4 Messaging
- 9.5 Data Replication
- 9.6 Interfaces: Internal and External
- 9.7 Conclusion
-
10 Architecture of Individual Microservices
- 10.1 Domain Architecture
- 10.2 CQRS
- 10.3 Event Sourcing
- 10.4 Hexagonal Architecture
- 10.5 Resilience and Stability
- 10.6 Technical Architecture
- 10.7 Conclusion
-
11 Testing Microservices and Microservice-based Systems
- 11.1 Why Tests?
- 11.2 How to Test?
- 11.3 Mitigate Risks at Deployment
- 11.4 Testing the Overall System
- 11.5 Testing Legacy Applications and Microservices
- 11.6 Testing Individual Microservices
- 11.7 Consumer-driven Contract Tests
- 11.8 Testing Technical Standards
- 11.9 Conclusion
-
12 Operations and Continuous Delivery of Microservices
- 12.1 Challenges Associated with the Operation of Microservices
- 12.2 Logging
- 12.3 Monitoring
- 12.4 Deployment
- Combined or Separate Deployment? (Jörg Müller)
- 12.5 Control
- 12.6 Infrastructure
- 12.7 Conclusion
-
13 Organizational Effects of a Microservices-based Architecture
- 13.1 Organizational Benefits of Microservices
- 13.2 An Alternative Approach to Conway’s Law
- 13.3 Micro and Macro Architecture
- 13.4 Technical Leadership
- 13.5 DevOps
- When Microservices Meet Classical IT Organizations (Alexander Heusingfeld)
- 13.6 Interface to the Customer
- 13.7 Reusable Code
- 13.8 Microservices Without Changing the Organization?
- 13.9 Conclusion
- Part IV: Technologies
-
14 Example for a Microservices-based Architecture
- 14.1 Domain Architecture
- 14.2 Basic Technologies
- 14.3 Build
- 14.4 Deployment Using Docker
- 14.5 Vagrant
- 14.6 Docker Machine
- 14.7 Docker Compose
- 14.8 Service Discovery
- 14.9 Communication
- 14.10 Resilience
- 14.11 Load Balancing
- 14.12 Integrating Other Technologies
- 14.13 Tests
- Experiences with JVM-based Microservices in the Amazon Cloud (Sascha Möllering)
- 14.14 Conclusion
-
15 Technologies for Nanoservices
- 15.1 Why Nanoservices?
- 15.2 Nanoservices: Definition
- 15.3 Amazon Lambda
- 15.4 OSGi
- 15.5 Java EE
- 15.6 Vert.x
- 15.7 Erlang
- 15.8 Seneca
- 15.9 Conclusion
-
16 How to Start with Microservices
- 16.1 Why Microservices?
- 16.2 Roads towards Microservices
- 16.3 Microservice: Hype or Reality?
- 16.4 Conclusion
-
1 Preface
- Notes
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
