I've been a Java developer for around 20 years, mostly working on enterprise backend systems. One thing I kept encountering across different projects was the same set of problems with event-driven applications. A database transaction succeeds, but publishing the event fails. A consumer processes the same message twice. A service crashes midway through processing, and suddenly recovery becomes complicated. The solutions often involve familiar patterns: transactional outbox, inbox, idempotency, retries, and recovery. But implementing and maintaining these patterns separately across applications takes time. So I started building NERV Event, an open-source Java/Spring Boot library that brings these reliability patterns together. The interesting part has been discovering how much harder it is to build a reusable library than to implement the same functionality inside a single application. I've had to think carefully about transaction boundaries, concurrency, API design, configuration validation, and what happens when an application crashes at the worst possible moment. It's still evolving, but building it has been a rewarding engineering side project. GitHub: https://github.com/czetsuyatech/nerv-event I'm particularly interested in feedback from developers who've built or maintained reusable libraries. What's been your biggest challenge when turning application-specific code into something other developers can reuse?   submitted by   /u/czetsuya [link]   [comments]