Jforum #116 - OpenTelemetry and cloud availability

We are excited to announce a meetup hosted by CAG.

Limited numbers of seats, REGISTRATION ONLY ON THIS LINK: https://jforum.confetti.events/jforum-116-meetup

Agenda:
17:30 Doors open, light food and drinks

18:00 OpenTelemetry and Continuous Feedback, things you need to know about your Java code in Runtime by Roni Dover

What do you know about the code changes that were just introduced into the codebase? When will you start noticing if something goes wrong? If there are so many accessible observability sources that can tell us what the code is doing, why are we using so little of that in our day-to-day coding?
Continuous Feedback is a new dev practice that aims to make practical usage of code runtime data to shorten the feedback loop during development. It enables developers to get early data about their code changes and detect issues and regressions as-they-code. At the same time, collecting data from multiple environments, allows developers to instantly understand how their code is performing in the real world.
In this session, we'll look past the novelty of using OSS observability tools and technologies, to discuss how we can actually make them useful for developers. We'll take a look at the benefits of enabling OpenTelemetry collection for dev and test data and examine OSS tools to help analyze the application runtime. Throughout the talk, we'll go over code examples of common anti-patterns, code smells, hidden errors, and other types of problems that observability can reveal - prior to merging a PR,
Ultimately, the goal should not be simply observing the application or creating nice-looking dashboards. Rather, success is in leveraging observability data in order to achieve a more effective dev process and write better code.

What do you know about the code changes that were just introduced into the codebase? When will you start noticing if something goes wrong? If there are so many accessible observability sources that can tell us what the code is doing, why are we using so little of that in our day-to-day coding?

18:50 Staying available in face of a cloud region catastrophe by Johan Andrén
A quick search for “outage” and any of the big cloud providers will show you that, while not daily, region outages happen. Building systems that run in the cloud but are still available to users during such outages is hard.

Replicated Event Sourcing combines Event Sourcing with CRDTs to make it possible to build stateful, active-active, entities - that can accept writes in multiple geographically distributed locations. Conflicting changes can be detected and resolved at a business logic level.
This can both provide high availability in the face of cloud region outages and low latency by keeping the state geographically close to the user.

In this talk we'll take a look at the concepts and main idea as well as looking at how an implementation can look like in Java.

19:45 Mingle