Name: Spring Modulith and WireQuery
Start: 2024-05-15T17:30:00+02:00
End: 2024-05-15T21:00:00+02:00
Location: Picnic HQ

**Agenda**

* 17:30 Doors opens, drinks, and food. Thanks **Picnic** for hosting us!
* 18:30 Talk 1 starts: "*Spring Modulith: slicing onions without crying*" by **[Pim Tegelaar](https://www.linkedin.com/in/pimtegelaar/)** (Picnic)
* 19:15 short break
* 19:30 Talk 2 starts: "*WireQuery: A better way to investigate bugs & understand how your systems behave*" by **[Wouter Nederhof](https://www.linkedin.com/in/wouter-nederhof-85942488/)** (Rabobank)
* 20:15 drinks & networking

***Information about the talks:***

Talk 1: "**Spring Modulith: slicing onions without crying"** by [Pim Tegelaar](https://www.linkedin.com/in/pimtegelaar/)

The architecture of an application fundamentally determines its maintainability, scalability, and overall quality. Spring, renowned for its versatility, empowers developers to align technical components with domain concepts, for more coherent and maintainable codebases.

This session explores how Spring Modulith amplifies these principles, offering developers a framework for crafting modular and maintainable Spring Boot applications. You will learn how to cleanly cut your architecture, validate the package structure with automated tests, and generate diagrams to create overview. We'll also showcase how Picnic benefits from using Spring Modulith!

Talk 2: **“WireQuery: A better way to investigate bugs & understand how your systems behave"** by [Wouter Nederhof](https://www.linkedin.com/in/wouter-nederhof-85942488/)

Have you ever added logging to your code to investigate a bug, waited 45 minutes for a code review, and waited for all the pipelines to complete, only to find out you still didn’t have enough information? Or better yet, have you ever had that experience, and it turned out the issue was actually in an upstream service, and therefore, the team upstream would have to re-do this process all over again?

I have. I’ve spent countless hours as a software engineer adding log statements to fix a bug and debug sessions with customers, only to find out we didn’t log the correct information. It’s frustrating, and yet, it happens every day!

To tackle this problem, I created [WireQuery](https://www.wirequery.io/). WireQuery lets you capture, explore, and analyze data flowing in and out of your applications. It does not compromise your services’ confidentiality because confidential fields are masked through field-level masking. Combined with front-end recording, WireQuery gives you all the information you need to reproduce (and therefore fix) virtually any bug.

In this talk, I’d like to discuss how this tool works, how it can be used, and hopefully save you countless hours from adding log statements to fix bugs.

Vladimir Dejanović

Ramon Wieleman

Geertjan Wielenga

Amsterdam Java User Group

Technology

Cloud Computing

Java

Open Source

Software Development

JavaScript

Web Technology

Web Development

Android Development Operating Systems Technology

Mobile Development

Front-end Development

Java Concurrency

Java Virtual Machine

HTML5

Spring Framework

Spring Modulith and WireQuery

Kotlin

Picnic HQ

Delen

Amsterdam Java User Group

Spring Modulith and WireQuery

Amsterdam Java User Group

Details

Leden zijn ook geïnteresseerd in