About us
Majug², the Mannheim Java User Group, was founded in 2008 and offers regular talks on Java-related topics about once a month. Every now and then we hold a CodeCamp to hone our coding skills and get to know a new technology. The meetings are usually held at the Mannheim University, after the talk, we have drinks and socialize in a nearby pub. Members come from all around Mannheim from an area which stretches from Karlsruhe to Walldorf, Darmstadt, and Frankfurt.
Please note that our main website is http://www.majug.de and we only use Meetup as a secondary site.
For the curious: the ² in Majug² stands for the squares which make up the layout of the inner city of Mannheim. See this Wikipedia article for details.
Featured event

Event Sourcing: Simpler Persistence Without ORMs
Abstract
Event Sourcing is not just a different way to persist data, but a different way of thinking about data. With ORMs like Hibernate, we have to consider query performance, fetch strategies, mapping domain models to database schemas, caching, etc. With Event Sourcing, we can use a few simple patterns to build our systems:
Commands: user actions representing an intention, e.g., “Buy Concert Ticket”
Events: meaningful changes to state as a result of executing Commands, e.g., “Ticket Purchased”
Read Models: up-to-date views of Events, derived specifically for a particular way of looking at the data, e.g., “My Tickets”, or “All Ticket Sales”
Need caching for the ticket sales report? That’s a Read Model. Display tickets for a Customer? That’s another Read Model, using the same principles to derive the desired view of state. Performance isn’t an issue, as replaying events is very fast. Even in a system with millions or billions of events, we only need to replay events related directly to a specific entity or state view.
You’ll see what makes Event Sourcing a mindshift rather than just a different persistence mechanism: updates are just appends to a log, mapping objects is no longer needed, and you keep the history of changes to data, so you can always know what happened and ask questions you didn’t expect to have.
Bio
Ted M. Young is a Java technical coach and live coder. He's been in software development for over 30 years, following eXtreme Programming practices since 2000. Ted loves helping folks make their code more testable and teaches Test-Driven Development (TDD), Refactoring, Domain-Driven Design, and Event Sourcing through hands-on, shared experiences. Ted created the acclaimed "JitterTed's TDD Game" used at events and companies worldwide to help people understand the nuances and benefits of TDD in a fun way.
https://ted.dev/about
https://www.linkedin.com/in/tedmyoung/
Eine Veranstaltung des iJUG e. V.
Upcoming events
1

Event Sourcing: Simpler Persistence Without ORMs
Technische Hochschule Mannheim, Paul-Wittsack-Straße 10, 68163 Mannheim, Germany, Mannheim, BW, DEAbstract
Event Sourcing is not just a different way to persist data, but a different way of thinking about data. With ORMs like Hibernate, we have to consider query performance, fetch strategies, mapping domain models to database schemas, caching, etc. With Event Sourcing, we can use a few simple patterns to build our systems:
Commands: user actions representing an intention, e.g., “Buy Concert Ticket”
Events: meaningful changes to state as a result of executing Commands, e.g., “Ticket Purchased”
Read Models: up-to-date views of Events, derived specifically for a particular way of looking at the data, e.g., “My Tickets”, or “All Ticket Sales”Need caching for the ticket sales report? That’s a Read Model. Display tickets for a Customer? That’s another Read Model, using the same principles to derive the desired view of state. Performance isn’t an issue, as replaying events is very fast. Even in a system with millions or billions of events, we only need to replay events related directly to a specific entity or state view.
You’ll see what makes Event Sourcing a mindshift rather than just a different persistence mechanism: updates are just appends to a log, mapping objects is no longer needed, and you keep the history of changes to data, so you can always know what happened and ask questions you didn’t expect to have.
Bio
Ted M. Young is a Java technical coach and live coder. He's been in software development for over 30 years, following eXtreme Programming practices since 2000. Ted loves helping folks make their code more testable and teaches Test-Driven Development (TDD), Refactoring, Domain-Driven Design, and Event Sourcing through hands-on, shared experiences. Ted created the acclaimed "JitterTed's TDD Game" used at events and companies worldwide to help people understand the nuances and benefits of TDD in a fun way.
https://ted.dev/about
https://www.linkedin.com/in/tedmyoung/Eine Veranstaltung des iJUG e. V.
8 attendees
Past events
70

