Downloaded 126 times
Uploaded byChristian Posta
Real world #microservices with Apache Camel, Fabric8, and OpenShift
This document discusses the concepts and technologies related to microservices, focusing on Apache Camel and Fabric8. It outlines the principles of microservices, integration patterns, and the advantages of using Apache Camel for building and managing microservices. The document also touches on challenges and methodologies for deploying microservices effectively in modern environments such as Kubernetes and OpenShift.
More Related Content
Similar to Real world #microservices with Apache Camel, Fabric8, and OpenShift
Real world #microservices with Apache Camel, Fabric8, and OpenShift
- 1. Real-world #microservices with ApacheCamel and Fabric8
- 3. Who? Christian Posta Principal MiddlewareSpecialist/Architect Blog: http://christianposta.com/blog Twitter: @christianposta Email: christian@redhat.com • Committer on Apache Camel, ActiveMQ, Fabric8, PMC on ActiveMQ • Author: Essential Camel Components DZone Refcard • Frequent blogger and speaker about open-source technology!
- 4. • Microservices • Heavylifting with Apache Camel • Managing microservices with Fuse, Fabric8 v1 • OpenShift, Fabric8 v2 • Beer (lots?) Agenda
- 5. Why do wecare?
- 9.
- 11. • Services, reuse,composition • Loose coupling! • Contracts • Incremental change • “Business Agility” SOA!
- 13. SOA made smaller…micro even… So what are microservices?
- 14. A term thathelps describe distributed systems that organically evolve into scalable, loosely coupled, modular sets of services that work together to deliver business value with acceptable tradeoffs. So what are microservices?
- 15. • If myservices are isolated at the process level, I’m doing #microservices • If I use REST/Thrift/ProtoBuf instead of SOAP, I’m doing #microservices • If I use JSON, I’m doing #microservices • If I use no-container / SpringBoot / Dropwizard / embedded Jetty, I’m doing #microservices I’m doing microservices if…
- 16. • Agile methodology •SOA principles • Domain Driven Design • Hexagonal Architectures • Pipes and Filters • Actor Model • REST • SEDA Microservices emerged as a result…
- 17. • Modularity! • Flexibletechnology options • “Smart endpoints” “dumb pipes” • Evolving design • Independently scalable • Automation, DevOps philosophy • Decentralized, choreographed interactions • Testable • Design for failure Microservices…
- 18. Isolation: logical orphysical?
- 19. • No silverbullet; distributed systems are *hard* • Dependency hell, custom shared libraries • Fragmented and inconsistent management • Team communication challenges • Health checking, monitoring, liveness • Over architecting, performance concerns, things spiraling out of control fast Challenges ahead…
- 20.
- 21. Real developers rideCamels!
- 22. 2 Apache Camel Apache Camelis an open-source, light-weight, integration library. Use Camel to integrate disparate systems that speak different protocols and data formats
- 23. Apache Camel Enterprise IntegrationPatterns http://camel.apache.org/eip
- 24. Features ● Enterprise IntegrationPatterns (EIPs) ● Domain Specific Language to write “flows” or “routes” ● Large collection of adapters/components for legacy systems, B2B, and SaaS ● Strong Unit test/Integration test framework ● Expression languages ● Data Formats ● Tooling with JBoss Developer Studio
- 25. Java DSL public classOrderProcessorRouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { from(“activemq:orders”) .choice() .when(header(“customer-rating”).isEqualTo(“gold”)) .to(“ibmmq:topic:specialCustomer”) .otherwise() .to(“ftp://user@host/orders/regularCustomers”) .end() .log(“received new order ${body.orderId}”) .to(“ibatis:storeOrder?statementType=Insert”); } }
- 26. Spring XML DSL <routeid=“processOrders”> <from uri=“activemq:orders”/> <choice> <when> <simple>${header.customer-rating} == ‘gold’</simple> <to uri=“wmq:topic:specialCustomer”> </when> <otherwise> <to uri=“ftp://user@host/orders/regularCustomers” /> </otherwise> </choice> <log message=“received new order ${body.orderId}”/> <to uri=“ibatis:storeOrder?statementType=Insert”/> </route>
- 27. Camel - JBossDeveloper Studio
- 28. • Dynamic routingoptions • REST DSL • Backpressure mechanisms • Loadbalancing algorithms / Circuit Breaker pattern Heavy Lifting: Camel for Microservices
- 29. • “Smart endpoints,dumb pipes” • Endpoint does one thing well • Metadata used for further routing • Really “dynamic” with rules engine (eg, Drools/BRMS) Dynamic Routing
- 30. • Content BasedRouter • Dynamic Router • Routing Slip • Recipient List Dynamic Routing
- 31. • Expressive wayto define REST endpoints • POST, REST, PUT • Auto binding to POJOs • Plugs into Swagger for interface definition/documentation • Uses configurable HTTP engine • camel-netty-http • camel-jetty • camel-reslet • camel-sevlet (deploy into other containers) • camel-spark-rest REST DSL (2.14)
- 32. REST DSL public classOrderProcessorRouteBuilder 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”); } }
- 33. • Backpressure isa way for a service to flow control callers • Detecting when can be difficult • Need to bound processing queues in a SEDA • Take advantage of built in TCP flow control for socket/http requests Backpressure with Camel
- 34. • Throttle EIP •http://camel.apache.org/throttler.html • Blocking SEDA Queue • from(“seda:name?size=100&blockWhenFull=true) • Configure jetty/netty to use blocking acceptor queues • https://wiki.eclipse.org/Jetty/Howto/High_Load • Using Exception handling/retry and DLQ logic when getting flow controlled • http://camel.apache.org/error-handling-in-camel.html Backpressure with Camel
- 35. • Useful tokeep from overloading a system (use in conjunction with backpressure if you can) • Smart loadbalancing • Sticky • Random • Failover • Circuit breaker Loadbalance/Circuit breaker
- 36. Circuit breaker Image fromhttp://martinfowler.com/bliki/CircuitBreaker.html
- 37. Circuit breaker public classOrderProcessorRouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { from(“direct:someinterface”) .loadbalance() .circuitBreaker(3, 20000L, MyException.class) .to(“ibatis:storeOrder?statementType=Insert”); } }
- 38. More Information ● Camelin Action ● Apache Camel Developer’s Cookbook ● Community website ○ http://camel.apache.org/
- 39. JBoss Fuse (RedHat product)
- 41. RED HAT JBOSSFUSE Development and tooling Develop, test, debug, refine, deploy JBoss Developer Studio Web services framework Web services standards, SOAP, XML/HTTP, RESTful HTTP Integration framework Transformation, mediation, enterprise integration patterns Management and monitoring System and web services metrics, automated discovery, container status, automatic updates JBoss Operations Network + JBoss Fabric Management Console (hawtio) Apache CXF Apache Camel Reliable Messaging JMS/STOMP/NMS/MQTT, publishing-subscribe/point-2-point, store and forward Apache ActiveMQ Container Life cycle management, resource management, dynamic deployment, security and provisioning Apache Karaf + Fuse Fabric RED HAT ENTERPRISE LINUX Windows, UNIX, and other Linux
- 42.
- 45. • Simplifies deployments •Provides centralized configuration • Versioning • Visualization of your middleware • Service discovery • Smart load balancing • Failover • Provides cluster capabilities, coordination http://fabric8.io
- 46. • Implemented withZookeeper and git • Intended to be used with a dynamic JVM/Apache Karaf • Profiles store configuration, metadata, end- state deployments • Networking, JVM isolation, orchestration, auto-scaling, health checks, cloud deployments: all up to you Fabric8 V1.x
- 47. • Registry • Whereconfigs are stored, everything centrally managed • Profiles • Description of end-state deployment of a server • Agent • Listens on the server that can respond to registry changes/profile updates Fabric8 V1.x
- 48.
- 49. • Implemented withDocker and Kubernetes • Use any JVM (or any technology) • Docker images, encourage static, well- defined, well-tested deployments • Provides networking, JVM isolation, orchestration, auto-scaling, health checks, cloud deployments • Still in community! Proving this out! Fabric8 V2
- 50. Docker / LinuxContainers
- 51.
- 53.
- 55. • Pods • Services •Replication Controllers Kubernetes
- 56. Red Hat’s PaaS:OpenShift Public PaaS Service On-premise or Private PaaS Software Open Source PaaS Project
- 57. Scale IT Likea Factory with PaaS
- 58.
- 59.