Linked e-resources
Details
Table of Contents
At a Glance; Contents; About the Authors; About the Technical Reviewer; Acknowledgments; Introduction; Part I: Service Oriented Architectures; Chapter 1: Microservices: The What and the Why; All Successful Software Undergoes Change; Remember Service-Oriented Architectures?; What Is a Service?; What Are Microservices?; Microservices Are Not "CORBA over HTTP"; Industry Adoption of Microservices; Why Use Microservices?; Advantages as Seen by Industry Experts; Our Reasons to Adopt a Microservices Architecture; Potential Pitfalls and How to Avoid Them
When Should I Start with a Microservices Architecture?Summary; Chapter 2: Rules of Engagement; Customer-Facing Applications Cannot Directly Touch Any Data Store; No Service Accesses Another Service's Data Store; Invest in Making Spinning Up New Services Trivial; Build Services in a Consistent Way; Define API Contracts in Code; Every Service Has at Least a Development and a Production Instance; Existing Code Bases; Summary; Part II: APIs; Chapter 3: Partitioning Your Business into Services; General Approaches for Application Decomposition and Aggregation; Application Decomposition
Decomposing by FunctionalityDecomposing by Maturity; Decomposing by Data-Access Pattern; Decomposing by Context; Application Aggregation; Aggregation for a Derived Functionality; Aggregation for Business Intelligence; Aggregation for Client Convenience; Aggregation to Aid System Performance; When to Use Decomposition versus Aggregation?; Decomposing and Aggregating a Sample Application; Welcome to Our Bookstore!; Partitioning the Bookstore; Decomposing into Core Services; Applications and Aggregated Services; Supporting Platform Services; Feature-Focused Services; Summary
Chapter 4: Designing Your APIsIntroducing APIs; The Significance of API Design; Why is Designing a Good API Important?; What Makes an API Good?; General Characteristics; Clear Naming; Focus; Completeness; Intuitiveness; Consistency; Hypermedia Type; API Design Guide; Nonfunctional Requirements; Service-Level Agreements; Availability; Performance; Scalability, Capacity, Recoverability, and Reliability; Implementing APIs the Right Way; Gather Requirements; Maximize Information Hiding; APIs Change; Acknowledge and Accept Changes; The Development and Communication Process for Breaking Changes
Add a New APIVersion Your APIs; Negotiating the API Version; Using HTTP Headers; Using the Request Path; Using a Query Parameter; Determining What Numbering Scheme to Use; Supporting and Deprecating API Versions; Designing / Splitting Up by Example; The Bookstore Home Page; Cart Information; User Recommendations; The Book Detail Page; Book Details; Reviews; Images; Summary; Chapter 5: Defining APIs; Interface Definition Languages (IDLs); A Matter of Style: RPC versus REST; RPC-Style Interface Definition Languages; RESTful Interface Definition Languages; Our Stance
When Should I Start with a Microservices Architecture?Summary; Chapter 2: Rules of Engagement; Customer-Facing Applications Cannot Directly Touch Any Data Store; No Service Accesses Another Service's Data Store; Invest in Making Spinning Up New Services Trivial; Build Services in a Consistent Way; Define API Contracts in Code; Every Service Has at Least a Development and a Production Instance; Existing Code Bases; Summary; Part II: APIs; Chapter 3: Partitioning Your Business into Services; General Approaches for Application Decomposition and Aggregation; Application Decomposition
Decomposing by FunctionalityDecomposing by Maturity; Decomposing by Data-Access Pattern; Decomposing by Context; Application Aggregation; Aggregation for a Derived Functionality; Aggregation for Business Intelligence; Aggregation for Client Convenience; Aggregation to Aid System Performance; When to Use Decomposition versus Aggregation?; Decomposing and Aggregating a Sample Application; Welcome to Our Bookstore!; Partitioning the Bookstore; Decomposing into Core Services; Applications and Aggregated Services; Supporting Platform Services; Feature-Focused Services; Summary
Chapter 4: Designing Your APIsIntroducing APIs; The Significance of API Design; Why is Designing a Good API Important?; What Makes an API Good?; General Characteristics; Clear Naming; Focus; Completeness; Intuitiveness; Consistency; Hypermedia Type; API Design Guide; Nonfunctional Requirements; Service-Level Agreements; Availability; Performance; Scalability, Capacity, Recoverability, and Reliability; Implementing APIs the Right Way; Gather Requirements; Maximize Information Hiding; APIs Change; Acknowledge and Accept Changes; The Development and Communication Process for Breaking Changes
Add a New APIVersion Your APIs; Negotiating the API Version; Using HTTP Headers; Using the Request Path; Using a Query Parameter; Determining What Numbering Scheme to Use; Supporting and Deprecating API Versions; Designing / Splitting Up by Example; The Bookstore Home Page; Cart Information; User Recommendations; The Book Detail Page; Book Details; Reviews; Images; Summary; Chapter 5: Defining APIs; Interface Definition Languages (IDLs); A Matter of Style: RPC versus REST; RPC-Style Interface Definition Languages; RESTful Interface Definition Languages; Our Stance