About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action and the creator of the original CloudFoundry.com. His latest startup is eventuate.io, a microservices application platform.


Microservices consulting and training

Chris offers a comprehensive consulting services, workshops and hands on training classes to help you use microservices effectively.

Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and Kubernetes. Find out more


Microservices in Sydney and Melbourne

I'll be speaking at the YOW! conference and teaching a one day microservices workshop in Sydney and Melbourne. 10% discount with JOINMEATYOW18.

Learn more


Learn more about microservices

Chris offers a comprehensive set of resources for learning about microservices including articles, an O'Reilly training video, and example code.

Learn more


Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code


Get the book: Microservice patterns

</div> </div>
Signup for the newsletter

A new microservices application platform that solves distributed data management problems.
Join the [microservices google group](https://groups.google.com/forum/#!forum/microservices)

Pattern: Service Component Test

Context

You have applied the Microservice architecture pattern. The application consists of numerous services. Services often invoke other services. You must write automated tests that verify that a service behaves correctly.

Problem

How do you easily test a service?

Forces

  • End to end testing (i.e. tests that launch multiple services) is difficult, slow, brittle, and expensive.

Solution

A test suite that tests a service in isolation using test doubles for any services that it invokes.

Examples

Spring Cloud Contract is an open source project that supports this style of testing.

Resulting context

This pattern has the following benefits:

  • Testing a service in isolation is easier, faster, more reliable and cheap

This pattern has the following drawbacks:

  • Tests might pass but the application will fail in production

This pattern has the following issues:

  • How to ensure that the test doubles always correctly emulate the behavior of the invoked services?

See also


Copyright © 2017 Chris Richardson • All rights reserved • Supported by Kong.