1 / 16

Event-driven Microservices

Event-driven Microservices. Jeremy Deane http:// jeremydeane.net. Event-driven Architecture. Events Events represent a snapshot in time of an occurrence within a system Information ( noise ) to Actionable ( signal ) Enterprise Integration Patterns (EIP)

omalley
Download Presentation

Event-driven Microservices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Event-driven Microservices Jeremy Deane http://jeremydeane.net

  2. Event-driven Architecture • Events • Events represent a snapshot in time of an occurrence within a system • Information (noise) to Actionable (signal) • Enterprise Integration Patterns (EIP) • Event Message, Command Event, Event Sourcing • Middleware Solutions • ActiveMQ, RabbitMQ (JMS-AMPQ) • Kafka, ZeroMQ • Akka, Storm

  3. Microservices Architectural Style …an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. http://martinfowler.com/articles/microservices.html …you must be this tall to use. - Neal Ford

  4. Event-driven Microservices

  5. Apache ActiveMQ Integration Options Java Message Service (JMS) Advanced Message Queuing Protocol (AMQP) • Languages - Transport • Java-Scala – TCP/NIO • Ruby, Perl, Python – Stomp • C# (NMS) –TCP/NIO Deployment Flexibility Stand-alone Embedded Advanced Topologies Master-Slave High Availability (HA) Federated Network Support Active Open Source Community Commercial 24X7 Options

  6. ActiveMQ High Availability (HA) Messaging Backbone failover:(tcp://PrimaryBroker:61616,tcp://SecondaryBroker:61616)?randomize=false

  7. ActiveMQ Federated Topologies Web Security Network Segment • Network • Business • Other Service Security Network Segment Data Security Network Segment

  8. Apache Camel – Enterprise Integration Library Camel In Action by Claus Ibsen and Jonathan Anstey • Domain Specific Languages (DSL) – Java, Scala, Spring DSL • Route Builders – create Endpoints (i.e. from & to) using Components (e.g. protocol) and Processors (e.g. Mediation, Enrichment • Route Engine – Loads and executes Routes

  9. Spring Boot – Apache Camel Route Processing /** * Splitter - xpath expression */ from("activemq:emagic.orders"). split(splitXPath).parallelProcessing(). wireTap("direct:ministry"). to("activemq:emagic.order"); /** Spring Boot – Camel Route Application */ @Configuration @ImportResource("classpath:camel-route-spring.xml") public class MagicRouterApplication { public static void main(String[] args) { SpringApplication.run(MagicRouterApplication.class, args); } }

  10. Apache Camel – Deployment Options • Single Event-driven Microservice per VM • Multiple Event-Driven Microservices per VM • Single Event-driven Microservices Container (e.g. Docker or Rocket)

  11. Apache Camel – ActiveMQ Integration

  12. Event-driven Microservices: Demo

  13. Event-driven Microservices: Quality Assurance @Override protected CamelContextcreateCamelContext() throws Exception { CamelContext context = super.createCamelContext(); //setup routes to Mock Endpoints context.addRoutes(newRouteBuilder() { public void configure() { //test xpath split from ("direct:split"). split(newXPathBuilder (MagicRouteBuilder.splitXpath)). to("mock:order"); }); return context; } • Source Control Management - Git • Functional Tests - Camel Test Support • Continuous Integration (CI) – Team City @Test public void testSplitLogic() throws Exception { //Set expectations MockEndpoint order = getMockEndpoint("mock:order"); order.expectedMessageCount(3); //read in a small batch String xml = IOUtils.toString(this.getClass(). getResourceAsStream("batch.xml"), "UTF-8"); //execute the test template.sendBody("direct:split", xml); //should be three orders in the batch order.assertIsSatisfied(); }

  14. Event-driven Microservices: Release Engineering • Convention over Configuration • Deployment and Configuration Directory Structure • Linux init.d Symbolic Link • Git Hooks • Trigger Release Process and Functional Regression • Chef Recipes • Instantiate Linux VM • Provision Linux VM (Java Runtime Environment) • Deploy Executable JAR and Configurations

  15. Event-Driven Microservices: Operations • Logging (e.g. Splunk, Logstash) • Standard Format • Alerts • Processes (e.g. Zabbix, Nagios, Hyperic) • JMX • REST WS • Command Events • Synthetic Transactions • Tracking Identifier • Correlate activities across systems • Rapidly identify problems and performance bottlenecks • Command Consoles (e.g. ActiveMQ, Java Console, Zabbix, Splunk)

  16. Questions & Feedback Questions & Feedback Jeremy DeaneDirector of Software ArchitectureNaviNet jeremy.deane@gmail.com http://jeremydeane.net My Contact information: https://github.com/jtdeane/event-driven-microservices https://github.com/jtdeane/camel-standalone-router

More Related