6 Side notes JAX London 2016

11th Oct – 15:15 to 16:05 Event-driven Microservices

** Jeremy Deane, Liberty Mutual**

• Presentation slides
• Demo code
• Key concepts:
  • Events happen all the time and there are different kinds of events.
  • We look for actionable events.
  • Messages are events.
  • Micro-services is an architectural style.
  • Micro-services allow for good scalable systems, but at the cost of complex delivery and backward maintainability.
  • Do not refactor and implement new features at the same time.
  • Avoid single point of failure. One service per JVM. One Service discovery, Active MQ, A.Camel, … per container.
  • Add id/tokens on each message/event as a technique to log tracking the event’s route.
• Tools:
  • http://akka.io/ «resilient elastic distributed real-time transaction processing»
  • Active MQ: Apache Active MQ is an open source message broker written in Java together with a full Java Message Service (JMS) client.
  • Apache Camel: Apache Camel ™ is a versatile open-source integration framework based on known Enterprise Integration Patterns.
  • Camel testing has good integration with main Java testing tools
  • As a starting point for Apache Camel route, processing use Camel Spring Boot

That was all for this session. I hope it helps, please leave a comment if you would like to add something.

Posted by Marc Andreu Fernandez