Exploring Microservice Development
With chapters selected by John Carnell
  • March 2018
  • ISBN 9781617295591
  • 88 pages

Get into the microservices mindset without drowning in the details. Before you start writing code, you need to understand when a microservice architecture makes sense, what has to change in your team organization, and how this approach affects your build, test, and deploy process. There's plenty to learn when you get down to the nuts-and-bolts of building microservices; starting with the big picture makes the details a lot easier to grok.

Exploring Microservice Development is a collection of chapters from three Manning books. Hand-picked by senior cloud engineer John Carnell, this quick-start guide introduces the big picture of microservice design along with a high-level taste of operational concerns like debugging and testing. In it, you'll get a quick overview of decomposition strategies, a look into distributed tracing with Spring Cloud Sleuth and Zipkin for more efficient debugging, and over-the-wire service mocking using Mountebank. When you finish, you'll have a better idea of whether microservices are for you and what you need to get started.

Table of Contents detailed table of contents


Decomposition Strategies

Decomposition Strategies

2.1 The purpose of architecture

2.1.1 Why architecture matters

2.1.2 The microservice architecture’s an architectural style

2.1.3 Defining an application’s microservice architecture

2.2 Identifying the system operations

2.2.1 Creating a high-level domain model

2.2.2 Defining system operations

2.3 Strategies for decomposing an application into services

2.3.1 Decompose by business capability

2.3.2 Using scenarios to determine how the service collaborate

2.3.3 If only it were this easy…​

2.3.4 Decompose by sub-domain/bounded context

2.3.5 Decomposition guidelines

2.4 Summary

What’s inside:

Distributed Tracing with Spring Cloud Sleuth and Zipkin

Distributed Tracing with Spring Cloud Sleuth and Zipkin

9.1 Spring Cloud Sleuth and the correlation ID

9.1.1 Adding Spring Cloud sleuth to licensing and organization

9.1.2 Anatomy of a Spring Cloud Sleuth trace

9.2 Log aggregation and Spring Cloud Sleuth

9.2.1 A Spring Cloud Sleuth/Papertrail implementation in action

9.2.2 Create a Papertrail account and configure a syslog connector

9.2.3 Redirecting Docker output to Papertrail

9.2.4 Searching for Spring Cloud Sleuth trace IDs in Papertrail

9.2.5 Adding the correlation ID to the HTTP response with Zuul

9.3 Distributed tracing with Open Zipkin

9.3.1 Setting up the Spring Cloud Sleuth and Zipkin dependencies

9.3.2 Configuring the services to point to Zipkin

9.3.3 Installing and configuring a Zipkin server

9.3.4 Setting tracing levels

9.3.5 Using Zipkin to trace transactions

9.3.6 Visualizing a more complex transaction

9.3.7 Capturing messaging traces

9.3.8 Adding custom spans

9.4 Summary

What’s inside:

Testing Using Canned Responses

Testing Using Canned Responses

3.1 The Basics of Canned Responses

3.1.1 The Default Response

3.1.2 Understanding how the default response works

3.1.3 Changing the default response

3.1.4 Cycling through responses

3.2 HTTPS imposters

3.2.1 Setting up a trusted HTTPS imposter

3.2.2 Using mutual authentication

3.3 Saving the responses in a configuration file

3.3.1 Saving multiple imposters in the config file

3.4 Summary

What’s inside:


Promo page

What's inside

  • Decomposition Strategies from Microservice Patterns by Chris Richardson
  • Distributed tracing with Spring Cloud Sleuth and Zipkin from Spring Microservices in Action by John Carnell
  • Testing Using Canned Responses from Testing Microservices with Mountebank by Brandon Byars

About the author

John Carnell is a senior cloud engineer at Genesys, where he works in the PureCloud division. He spends most days building telephony-based microservices using the AWS platform using Java, Clojure, and Go. John is the author of Spring Microservices in Action.

eBook $0.00 PDF only

FREE domestic shipping on three or more pBooks