Chicago Microservices Integration Talk

Integration in the age of DevOps

5/11/16 Christian Posta @christianposta

Christian Posta Principal Middleware Specialist/Architect

Twitter: @christianposta

Blog: http://blog.christianposta.com

Email: [email protected]

•  Author “Microservices for Java developers” O’Reilly (June 2016)

•  Committer on Apache Camel, Apache ActiveMQ, Fabric8, many others

•  Worked with large Microservices, web-scale, unicorn company

•  Blogger, speaker about DevOps, integration, and microservices

Cloud Native Architectures

•  Trying to incorporate new technology? •  Trying to copy what others (Netflix, Amazon) are

doing? •  Tactical automation? •  Created a “DevOps” team? •  Exploring cloud services? •  Build/deploy automation? •  OpenSource? •  Piecemeal integration?

How are you keeping up with change?


Ifchangeishappeningontheoutsidefasterthanontheinsidetheendisinsight.

Jack Welch, former CEO, GE


S&P company life expectancy


Source: Dave Gray, The Connected Company

DevOps is NOT about efficiency. DevOps is a reorg.


•  Faster software delivery •  Own database (data) •  Faster innovation •  Scalability •  Right technology for the

problem •  Test individual services •  Isolation •  Individual deployments

Microservices helps solve the problem of “how do we decouple our services and teams to move quickly at scale to deliver business value”


•  If my services are isolated at the process level, I’m doing #microservices

I’m doing microservices if…

•  If I use REST/Thrift/ProtoBuf instead of SOAP, I’m doing #microservices

•  If I use JSON, I’m doing #microservices •  If I use Docker / SpringBoot / Dropwizard /

embedded Jetty, I’m doing #microservices

PeopletrytocopyNet7lix,buttheycanonlycopywhattheysee.Theycopytheresults,nottheprocess.

Adrian Cockcroft, former Chief Cloud Architect, Netflix

Callitwhatyouwant;SOA,microservices–it’salljustdistributedsystems

Christian Posta – Red Hat



Fallacies of distributed computing •  Reliable networking •  Latency is zero •  Bandwidth is infinite •  Network is secure •  Topology doesn’t change •  Single administrator •  Transport cost is zero •  Network is homogenous

https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing


If we have to take into account the network, do we still need integration?


We’ll just do reactive, event-driven distributed systems… still need integration?


Yes; we need reliable integration! •  REST, RPC •  Messaging (ActiveMQ, JMS, AMQP, STOMP, Kafka, etc) •  Legacy (SOAP, mainframe, file processing, proprietary) •  Managed file processing •  Streaming •  Message transformation •  EIPs

Heavy Lifting: Apache Camel for Microservices


Apache Camel to the rescue! •  Small Java library •  Distributed-system swiss-army knife! •  Powerful EIPs •  Declarative DSL •  Embeddable into any JVM (EAP, Karaf, Tomcat, Spring

Boot, Dropwizard, Wildfly Swarm, no container, etc) •  Very popular (200+ components for “dumb pipes”)

Real developers ride Camels!


Apache Camel to the rescue!

•  Automatic retries, backoff algorithms •  Dynamic routing •  Powerful testing/mocking framework •  Circuit breakers •  Backpressure mechanisms •  Beautiful REST DSL with built in Swagger support

REST DSL

public class OrderProcessorRouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { rest().post(“/order/socks”)

.description(“New Order for pair of socks”).consumes(“application/json”).route() .to(“activemq:topic:newOrder”) .log(“received new order ${body.orderId}”)

.to(“ibatis:storeOrder?statementType=Insert”); }}


Quick Demo of Camel


Typical problems developing microservices •  How to run them all locally? •  How to package them (dependency management) •  How to test? •  Vagrant? VirtualBox? VMs? •  Specify configuration •  Process isolation •  Service discovery •  Multiple versions?


Shared infrastructure platforms headaches

•  Different teams •  Different rates of change •  VM sprawl •  Configuration drift •  Isolation / multi-tenancy

•  Performance •  Real-time vs batch •  Compliance •  Security •  Technology choices


Immutable infrastructure/deploys •  “we’ll just put it back in Ansible/Chef/Puppet/Salt”

•  Avoid chucking binaries / configs together and hope!

•  Cattle vs Pets

•  Don’t change it; replace it

•  System created fully from automation; avoid drift

•  Eliminate manual configuration/intervention

Docker / Linux Containers

Kubernetes

•  Developer focused workflow •  Enterprise ready •  Higher level abstraction above containers for

delivering technology and business value •  Build/deployment triggers •  Software Defined Networking (SDN) •  Docker native format/packaging •  CLI/Web based tooling

OpenShift

Red Hat OpenShift

Public PaaS Service

On-premise or Private PaaS Software

Open Source PaaS Project


Fuse Integration Services for OpenShift

•  Set of tools for integration developers

•  Package your Fuse/Camel services as Docker images

•  Run locally on CDK (container development kit)

•  Manage them with Kubernetes/OpenShift

•  Flat class loader JVMs

•  Supports Spring, CDI, Blueprint

•  Plugs-in to your existing build/release ecosystem

(Jenkins/Maven/Nexus/Gitlab,etc)


Typical problems developing microservices •  How to run them all locally? •  How to package them •  How to test? •  Vagrant? VirtualBox? VMs? •  Specify configuration •  Process isolation •  Service discovery •  Multiple versions?


Quick Demo?

•  Trying to incorporate new technology? •  Trying to copy what others (Netflix, Amazon) are

doing? •  Tactical automation? •  Created a “DevOps” team? •  Exploring cloud services? •  Build/deploy automation? •  OpenSource? •  Piecemeal integration?

How are you keeping up with change?


•  100% open source, ASL 2.0 •  Technology agnostic (java, nodejs, python,

golang, etc) •  Built upon decades of industry practices •  1-click automation •  Cloud native (on premise, public cloud, hybrid) •  Complex build/deploy pipelines (human

workflows, approvals, chatops, etc) •  Comprehensive integration inside/outside the

platform

What if you could do all of this right now with an open-source platform?

•  Docker native, built on top of Kubernetes

•  1-click CI/CD •  Logging, Metrics •  ChatOps •  API Management •  iPaaS/Integration •  Chaos Monkey •  Lots and lots of tooling/

libraries to make developing cloud-native applications easier

http://fabric8.io

Christian Posta Principal Middleware Specialist/Architect

Twitter: @christianposta

Blog: http://blog.christianposta.com

Email: [email protected]

Questions, Discussion, Demo!

Chicago Microservices Integration Talk

Software

Transcript of Chicago Microservices Integration Talk