Integration Patterns for Microservices Architectures

Integration Patterns forMicroservices Architectures

NATS in the [Multi-Cloud] Enterprise

David WilliamsCo-Founder & Partner Williams & Garcia

@DavWilliams

NATS in the [Multi-Cloud] Enterprise Integration Patterns for Microservices ArchitecturesNATS in the [Multi-Cloud] Enterprise

Williams & Garcia“Full-stack” consultants based in Atlanta, GA.

Leveraging the ecosystem of modern application technologies to improve the development, deployment, and operability of enterprise applications.

NATS in the [Multi-Cloud] Enterprise Integration Patterns for Microservices Architectures

My background:sysadmin, architect <- consultant -> product dev

My 20+ years in the industry:application infrastructure aka middleware aka platforms, and the infrastructure they depend on.

My passion:traditional enterprise it -> disruptive technologies


what’s this NATS thing?Introduced to NATS through Cloud Foundry


pos·si·bil·i·tiesthings that may be chosen or done out of several possible alternatives.


A pattern catalog describing 65 integration patterns

Source: http://www.enterpriseintegrationpatterns.com/patterns/messaging/


• Applications were tightly-coupled

• Applications were large monoliths

• Enterprise applications were written in a single language, the majority in Java

• Messaging systems were big and complex

These patterns were “harvested” and documented in a time when …


anti-patternsproblem -> bad solution


the most common anti-patternin microservices architectures

StovepipeWhen existing software systems are migrated to a distributed infrastructure. Arises when converting the existing software interfaces to distributed interfaces.


Example of likely anti-patterns for microservices architectures

Any patterns that is transactional in nature:Transactional Client, Competing Consumers, Message Expiration

Any pattern that requires the messaging system to persist messages:Durable Subscriber, *Guaranteed Delivery, Claim Check

Any pattern where the messaging system inspects or modifies messages, selectively routes message, or transforms message content:Message Filter, Content Enricher, Content-Based Routing, Recipient List, Routing Slip and Process Manager


* For a opinion of the fallacy of “Guaranteed Delivery”, visit: http://bravenewgeek.com/what-you-want-is-what-you-dont-understanding-trade-offs-in-distributed-messaging/


so what are “good”patterns for

micromessaging?


Basic design patterns you’re already familiar with…

Publish / Subscribe

Queueing

Request / ReplySource: http://www.slideshare.net/derekcollison/nats-a-new-nervous-system-for-distributed-cloud-platforms


putting those patternsto usewith NATS


Design Pattern: Interservice Communication

Microservices communicate with each other via NATS messages. All business and routing logic in the service, not the messaging system.


Design Pattern: Control Plane

Service state changes triggered by receipt of messages from “controller” service.


Design Pattern: Heartbeat

Each microservice publishes heartbeat (health) information via NATS.


Design Pattern: Real-Time Stream Processing

Ingest through NATS into stream processor. Output processed stream via NATS to a SSE microservice.


Design Pattern: Event Store

Data written to, updated, or deleted from data store. Notification message of event change sent via NATS.


Design Pattern: Data Pump

Universal “database driver” using microservices as data writers/readers


let’s go global


Design Pattern: Bridgehead

Information exchange between different sites/regions via NATS


why should developershave all the fun?


Design Pattern: DevOps Gone Wild

Messaging as part of the infrastructure engineering & the DevOps toolchain


Design Pattern: Global Domination

All services, everywhere, communicating via NATS


don’t be like this guy


in summaryMicroservices architectures provide an

opportunity to re-evaluate the way we think about communication in the composable enterprise.


resourcesProject site:http://nats.io/

Referenced in deck:http://bravenewgeek.com/what-you-want-is-what-you-dont-understanding-trade-offs-in-distributed-messaging/ http://slideshare.net/derekcollison/nats-a-new-nervous-system-for-distributed-cloud-platforms

Get it here:http://nats.io/download/ https://hub.docker.com/_/nats/ https://github.com/nats-io/gnatsd


questions?

Integration Patterns for Microservices Architectures

Technology

Transcript of Integration Patterns for Microservices Architectures