book

Microservice APIs

by Jose Haro

February 2023

Intermediate to advanced

440 pages

12h 20m

English

Manning Publications

Read now

Unlock full access

prefaceacknowledgmentsabout this bookWho should read this book?How this book is organized: A roadmapAbout the codeliveBook discussion forumOther online resourcesabout the authorabout the cover illustration
1.1 What are microservices?1.1.1 Defining microservices1.1.2 Microservices vs. monoliths1.1.3 Microservices today and how we got here1.2 What are web APIs?1.2.1 What is an API?1.2.2 What is a web API?1.2.3 How do APIs help us drive microservices integrations?1.3 Challenges of microservices architecture1.3.1 Effective service decomposition1.3.2 Microservices integration tests1.3.3 Handling service unavailability1.3.4 Tracing distributed transactions1.3.5 Increased operational complexity and infrastructure overhead1.4 Introducing documentation-driven development1.5 Introducing the CoffeeMesh application1.6 Who this book is for and what you will learnSummary
2.1 Introducing the orders API specification2.2 High-level architecture of the orders application2.3 Implementing the API endpoints2.4 Implementing data validation models with pydantic2.5 Validating request payloads with pydantic2.6 Marshalling and validating response payloads with pydantic2.7 Adding an in-memory list of orders to the APISummary
3.1 Introducing CoffeeMesh3.2 Microservices design principles3.2.1 Database-per-service principle3.2.2 Loose coupling principle3.2.3 Single Responsibility Principle3.3 Service decomposition by business capability3.3.1 Analyzing the business structure of CoffeeMesh3.3.2 Decomposing microservices by business capabilities3.4 Service decomposition by subdomains3.4.1 What is domain-driven design?3.4.2 Applying strategic analysis to CoffeeMesh3.5 Decomposition by business capability vs. decomposition by subdomainSummary

4.1 What is REST?4.2 Architectural constraints of REST applications4.2.1 Separation of concerns: The client-server architecture principle4.2.2 Make it scalable: The statelessness principle4.2.3 Optimize for performance: The cacheability principle4.2.4 Make it simple for the client: The layered system principle4.2.5 Extendable interfaces: The code-on-demand principle4.2.6 Keep it consistent: The uniform interface principle4.3 Hypermedia as the engine of application state4.4 Analyzing the maturity of an API with the Richardson maturity model4.4.1 Level 0: Web APIs à la RPC4.4.2 Level 1: Introducing the concept of resource4.4.3 Level 2: Using HTTP methods and status codes4.4.4 Level 3: API discoverability4.5 Structured resource URLs with HTTP methods4.6 Using HTTP status codes to create expressive HTTP responses4.6.1 What are HTTP status codes?4.6.2 Using HTTP status codes to report client errors in the request4.6.3 Using HTTP status codes to report errors in the server4.7 Designing API payloads4.7.1 What are HTTP payloads, and when do we use them?4.7.2 HTTP payload design patterns4.8 Designing URL query parametersSummary
5.1 Using JSON Schema to model data5.2 Anatomy of an OpenAPI specification5.3 Documenting the API endpoints5.4 Documenting URL query parameters5.5 Documenting request payloads5.6 Refactoring schema definitions to avoid repetition5.7 Documenting API responses5.8 Creating generic responses5.9 Defining the authentication scheme of the APISummary
6.1 Overview of the orders API6.2 URL query parameters for the orders API6.3 Validating payloads with unknown fields6.4 Overriding FastAPI’s dynamically generated specification6.5 Overview of the kitchen API6.6 Introducing flask-smorest6.7 Initializing the web application for the API6.8 Implementing the API endpoints6.9 Implementing payload validation models with marshmallow6.10 Validating URL query parameters6.11 Validating data before serializing the response6.12 Implementing an in-memory list of schedules6.13 Overriding flask-smorest’s dynamically generated API specificationSummary
7.1 Hexagonal architectures for microservices7.2 Setting up the environment and the project structure7.3 Implementing the database models7.4 Implementing the repository pattern for data access7.4.1 The case for the repository pattern: What is it, and why is it useful?7.4.2 Implementing the repository pattern7.5 Implementing the business layer7.6 Implementing the unit of work pattern7.7 Integrating the API layer and the service layerSummary
8.1 Introducing GraphQL8.2 Introducing the products API8.3 Introducing GraphQL’s type system8.3.1 Creating property definitions with scalars8.3.2 Modeling resources with object types8.3.3 Creating custom scalars8.4 Representing collections of items with lists8.5 Think graphs: Building meaningful connections between object types8.5.1 Connecting types through edge properties8.5.2 Creating connections with through types8.6 Combining different types through unions and interfaces8.7 Constraining property values with enumerations8.8 Defining queries to serve data from the API8.9 Altering the state of the server with mutationsSummary
9.1 Running a GraphQL mock server9.2 Introducing GraphQL queries9.2.1 Running simple queries9.2.2 Running queries with parameters9.2.3 Understanding query errors9.3 Using fragments in queries9.4 Running queries with input parameters9.5 Navigating the API graph9.6 Running multiple queries and query aliasing9.6.1 Running multiple queries in the same request9.6.2 Aliasing our queries9.7 Running GraphQL mutations9.8 Running parameterized queries and mutations9.9 Demystifying GraphQL queries9.10 Calling a GraphQL API with Python codeSummary
10.1 Analyzing the API requirements10.2 Introducing the tech stack10.3 Introducing Ariadne10.4 Implementing the products API10.4.1 Laying out the project structure10.4.2 Creating an entry point for the GraphQL server10.4.3 Implementing query resolvers10.4.4 Implementing type resolvers10.4.5 Handling query parameters10.4.6 Implementing mutation resolvers10.4.7 Building resolvers for custom scalar types10.4.8 Implementing field resolversSummary
11.1 Setting up the environment for this chapter11.2 Understanding authentication and authorization protocols11.2.1 Understanding Open Authorization11.2.2 Understanding OpenID Connect11.3 Working with JSON Web Tokens11.3.1 Understanding the JWT header11.3.2 Understanding JWT claims11.3.3 Producing JWTs11.3.4 Inspecting JWTs11.3.5 Validating JWTs11.4 Adding authorization to the API server11.4.1 Creating an authorization module11.4.2 Creating an authorization middleware11.4.3 Adding CORS middleware11.5 Authorizing resource access11.5.1 Updating the database to link users and orders11.5.2 Restricting user access to their own resourcesSummary
12.1 Setting up the environment for API testing12.2 Testing REST APIs with Dredd12.2.1 What is Dredd?12.2.2 Installing and running Dredd’s default test suite12.2.3 Customizing Dredd’s test suite with hooks12.2.4 Using Dredd in your API testing strategy12.3 Introduction to property-based testing12.3.1 What is property-based testing?12.3.2 The traditional approach to API testing12.3.3 Property-based testing with Hypothesis12.3.4 Using Hypothesis to test a REST API endpoint12.4 Testing REST APIs with Schemathesis12.4.1 Running Schemathesis’s default test suite12.4.2 Using links to enhance Schemathesis’ test suite12.5 Testing GraphQL APIs12.5.1 Testing GraphQL APIs with Schemathesis12.6 Designing your API testing strategySummary
13.1 Setting up the environment for this chapter13.2 Dockerizing a microservice13.3 Running applications with Docker Compose13.4 Publishing Docker builds to a container registrySummary
14.1 Setting up the environment for this chapter14.2 How Kubernetes works: The “CliffsNotes” version14.3 Creating a Kubernetes cluster with EKS14.4 Using IAM roles for Kubernetes service accounts14.5 Deploying a Kubernetes load balancer14.6 Deploying microservices to the Kubernetes cluster14.6.1 Creating a deployment object14.6.2 Creating a service object14.6.3 Exposing services with ingress objects14.7 Setting up a serverless database with AWS Aurora14.7.1 Creating an Aurora Serverless database14.7.2 Managing secrets in Kubernetes14.7.3 Running the database migrations and connecting our service to the database14.8 Updating the OpenAPI specification with the ALB’s hostname14.9 Deleting the Kubernetes clusterSummary
A.1 The dawn of APIs: RPC, XML-RPC, and JSON-RPCA.2 SOAP and the emergence of API standardsA.3 RPC strikes again: Fast exchanges over gRPCA.4 HTTP-native APIs with RESTA.5 Granular queries with GraphQL
B.1 Versioning strategies for evolving APIsB.2 Managing the life cycle of your APIs
C.1 Using an identity as a service providerC.2 Using the PKCE authorization flowC.3 Using the client credentials flowC.4 Authorizing requests in the Swagger UI

Content preview from Microservice APIs

5 Documenting REST APIs with OpenAPI

This chapter covers

Using JSON Schema to create validation models for JSON documents
Describing REST APIs with the OpenAPI documentation standard
Modeling the payloads for API requests and responses
Creating reusable schemas in OpenAPI specifications

In this chapter, you’ll learn to document APIs using OpenAPI: the most popular standard for describing RESTful APIs, with a rich ecosystem of tools for testing, validating, and visualizing APIs. Most programming languages have libraries that support OpenAPI specifications, and in chapter 6 you’ll learn to use OpenAPI-compatible libraries from the Python ecosystem.

OpenAPI uses JSON Schema to describe an API’s structure and models, so we start by providing an ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Start your free trial

API Design Patterns

John J. Geewax

GraphQL in Action

Samer Buna

Designing APIs with Swagger and OpenAPI

Lukas Rosenstock, Joshua Ponelat

The Design of Web APIs

Arnaud Lauret

Publisher Resources

ISBN: 9781617298417Supplemental Content Publisher Support Other Publisher Website Supplemental Content Purchase Link