Sooner or later, there comes the time to measure how your RESTful service behaves under load. There are many out of the shelf tools, that allow to do this in "quick-and-dirty" way — like wrk / wrk2, ab, etc. However, if you’re working with JVM and want to setup reproducible and comprehensive load testing, probably, the best tool would be Gatling.
So, this post is how-to article for setting up load testing of Spring Boot service with Gatling.
Suppose, you have a task to implement dynamic routes configuration with Apache Camel. Or more concretely, you want to create Camel routes without having to add new route definitions just by changing configuration.
I recently encountered similar task, and as it turned out — there is a simple way to get things done . So, in this post I will share the solution.
Different people mean different things, when they talk about observability. To stay practical and concrete, by observability I mean monitoring, tracing and logging. In this post I will give recipe of adding monitoring to your Spring Boot service with Prometheus and Grafana.
TL;DR If you prefer reading code vs reading posts — just follow this link.