Log In
Or create an account -> 
Imperial Library
  • Home
  • About
  • News
  • Upload
  • Forum
  • Help
  • Login/SignUp

Index
Preface
Who Should Read This Book What’s In This Book
The Outline
What’s Not In This Book Conventions Used in This Book Safari® Books Online How to Contact Us Acknowledgments
I. Understanding Microservices 1. The Microservices Way
Understanding Microservices Adopting Microservices
“What are microservices? Don’t I already have them?” “How could this work here?” “How would we deal with all the parts? Who is in charge?”
The Microservices Way
The Speed of Change The Safety of Change At Scale In Harmony
Summary
2. The Microservices Value Proposition
Microservice Architecture Benefits Deriving Business Value Defining a Goal-Oriented, Layered Approach
Modularized Microservice Architecture Cohesive Microservice Architecture Systematized Microservice Architecture Maturity Model for Microservice Architecture Goals and Benefits
Applying the Goal-Oriented, Layered Approach Summary
II. Microservice Design Principles 3. Designing Microservice Systems
The Systems Approach to Microservices
Service Solution Process and Tools Organization Culture Embracing Change Putting it Together: The Holistic System Standardization and Coordination
Standardizing process Standardizing outputs Standardizing people Standardization trade-offs
A Microservices Design Process
Set Optimization Goals Development Principles Sketch the System Design Implement, Observe, and Adjust The Microservices System Designer Summary
4. Establishing a Foundation
Goals and Principles
Goals for the Microservices Way
Reduce cost Increase release speed Improve resilience Enable visibility Trade-offs
Operating Principles
Netflix Unix Suggested principles
Platforms
Shared Capabilities Local Capabilities
Culture
Focus on Communication Aligning Your Teams Fostering Innovation
Summary
III. Microservices in Practice 5. Service Design
Microservice Boundaries
Microservice Boundaries and Domain-Driven Design Bounded Context Smaller Is Better Ubiquitous Language
API Design for Microservices
Messsage-Oriented Hypermedia-Driven
Data and Microservices
Shipping, Inc. Event Sourcing System Model for Shipping, Inc. CQRS
Distributed Transactions and Sagas Asynchronous Message-Passing and Microservices Dealing with Dependencies
Pragmatic Mobility
Summary
6. System Design and Operations
Independent Deployability More Servers, More Servers! My Kingdom for a Server! Docker and Microservices The Role of Service Discovery The Need for an API Gateway
Security Transformation and Orchestration Routing
Monitoring and Alerting Summary
7. Adopting Microservices in Practice
Solution Architecture Guidance
How many bug fixes/features should be included in a single release? When do I know our microservice transformation is done?
Organizational Guidance
How do I know if my organization is ready for microservices?
Culture Guidance
How do I introduce change? Can I do microservices in a project-centric culture? Can I do microservices with outsourced workers?
Tools and Process Guidance
What kinds of tools and technology are required for microservices? What kinds of practices and processes will I need to support microservices? How do I govern a microservice system?
Services Guidance
Should all microservices be coded in the same programming language? What do I do about orphaned components?
Summary
8. Epilogue A. Microservice Architecture Reading List
Microservices 101 Best Practices Example Implementations Foundations
Index
  • ← Prev
  • Back
  • Next →
  • ← Prev
  • Back
  • Next →

Chief Librarian: Las Zenow <zenow@riseup.net>
Fork the source code from gitlab
.

This is a mirror of the Tor onion service:
http://kx5thpx2olielkihfyo4jgjqfb7zx7wxr3sd4xzt26ochei4m6f7tayd.onion