About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.

Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training classes and workshops.

Signup for the newsletter


LEARN about microservices

Chris offers numerous resources for learning the microservice architecture.

Training classes

Chris teaches comprehensive workshops and training classes for executives, architectures and developers to help your organization use microservices effectively. Learn how to avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and Kubernetes.


Get the book: Microservice patterns

Read Chris Richardson's book:

Example microservices applications

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

BUILD microservices

Ready to start using the microservice architecture?

Consulting services

Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,


The Eventuate platform

Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.

Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.

ASSESS your architecture

Assess your application's microservice architecture and identify what needs to be improved.

Consulting services

Engage Chris to conduct an architectural assessment.


Self assessment

Alternatively, conduct a self-assessment using the Microservices Assessment Platform.


Join the microservices google group

Pattern: Transaction log tailing

Context

You have applied the Transactional Outbox pattern.

Problem

How to publish messages/events into the outbox in the database to the message broker?

Forces

Solution

Tail the database transaction log and publish each message/event inserted into the outbox to the message broker.

The mechanism for trailing the transaction log depends on the database:

  • MySQL binlog
  • Postgres WAL
  • AWS DynamoDB table streams

Example

Resulting context

This pattern has the following benefits:

  • No 2PC
  • Guaranteed to be accurate

This pattern has the following drawbacks:

  • Relatively obscure although becoming increasing common
  • Requires database specific solutions
  • Tricky to avoid duplicate publishing

Learn more


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