Organised by: Arnhem Java User Group (ArnhemJUG)
Location: Stadsvilla Sonsbeek, Arnhem, the Netherlands.
Presentations:
-
Debugging distributed systems
Nowadays, most software projects are distributed systems: components are located on different networked computers which communicate and coordinate their actions by passing messages. Debugging distributed systems is not easy. When two components don’t play nice together, the cause could be virtually anything: software, DNS, routing, firewalls, proxies, load balancers, TLS.. and more!In this talk, I’ll share my experience with debugging distributed systems. We’ll look at typical issues and share ways to debug those issues and find their root causes. We’ll dive into networking, infrastructure, logging/tracing/metrics, testing, remote debugging and more. I’ll share lots of examples and war stories along the way. After this talk, you’ll have practical knowledge on how and where to get started with debugging distributed systems yourself!
About Bert Jan Schrijver
Bert Jan is CTO at OpenValue and focuses on Java, software architecture, Continuous Delivery and DevOps. Bert Jan is a Java Champion, JavaOne Rock Star speaker, Duke’s Choice Award winner and leads NLJUG, the Dutch Java User Group. He loves to share his experience by speaking at conferences, writing for the Dutch Java magazine and helping out Devoxx4Kids with teaching kids how to code.
-
From App to Services: moving a team to own the SLO
Many development teams are application developers. And it is far from a service in production. Nowadays, between devops, open APIs and information systems built around APIs, we are all becoming responsible for a running service.This presentation offers a transition journey retrospective of a Red Hat team that went from building products to delivering a cloud service able to run thousands of instances for others. We will share experience forged and all we had to (un)learn along the way.
This isn’t so much the code that changes, it’s the team culture and the conception of systems surrounding and supporting the code. What’s the impact on architecture? How are Standard Operating Procedures built? How does one define a SLA? How and why think about blast radius, noisy neighbors, SRE ? How to think about risks? etc.
After this presentation, you will have keys to think about your team’s transition to a model where everyone owns the SLO (Service Level Objective) of which (un)availability is part of.
About Emmanuel Bernard
Emmanuel is Java Champion, Distinguished Engineer and Chief Architect Application Cloud Services at Red Hat. His work is Open Source. He is most well known for his contributions and lead of the Quarkus and Hibernate projects as well as his contribution to Java standards.
His most recent endeavour is building a Kafka as a Service managed by Red Hat. Prior to that was Quarkus (A Kubernetes Native Java stack tailored for GraalVM & OpenJDK HotSpot, crafted from the best of breed Java libraries and standards).
He speaks regularly at various conferences and JUGs, including JavaOne, Red Hat Summit and Devoxx. He hosts several podcasts including Les Cast Codeurs.