6 Side notes JAX London 2016

Quick notes from session 6 of JAX London 2016. Event-driven Microservices preseneted by Jeremy Deane.

Dec 27, 2016· Q.Assistance · 1 minutes· Sep 20, 2024

Overview

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.

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.

Many thanks for reading, please leave a comment if you have any quality hint.

Keep on testing, better!

Automating bugs

Executing a set of SQL updates in order to prepare test data can be harmful. Legacy systems can be hard to maintain, improve, and expand because there is a general lack of understanding of the system.
Experiment-driven development

After years of practising in the test automation ecosystem, an axiom crystallized in my mind.
Integrating Google Sheets with Astro

A Simple Form Data Solution to learn and practice how to use Google Sheets as the backend for Astro web applications. For example to store simple forms data like contact forms or Call To Actions.