Getter methods retrieve state, while setter methods change state. We all know that. HTTP GET requests retrieve state, while HTTP POST requests change state. We all know that. Then why have we built so many applications with a single object model, blatantly ignoring this separation? Turns out that creating a separate model for reading and writing makes a lot of sense. But how can we introduce this concept into legacy applications? This presentation shows how to do it, and what is in it for you.

Getter methods retrieve state, while setter methods change state. We all know that. HTTP GET requests retrieve state, while HTTP POST requests change state. We all know that. Then why have we built so many applications with a single object model, blatantly ignoring this separation? Turns out that creating a separate model for reading and writing makes a lot of sense. But how can we introduce this concept into legacy applications? This presentation shows how to do it, and what is in it for you.

There has been much talk lately about Event-Driven architectures, Domain-Driven Design, CQRS, and Event Sourcing in particular. Even though those concepts are somehow related, understanding them does not get easier when mixing them up. In this workshop, we will go in-depth with Event Sourcing, briefly touching on related concepts to understand how they relate. Do you believe one could create a full-blown persistence solution with less than 400 lines of code? With Event Sourcing, we can. Come and see for yourself, we will code a working solution live in less than half a day. In the afternoon, it will be your turn to write code and put Event Sourcing to work yourself. While working on the exercise, you will be individually coached by the trainer. Every question will be answered! Make sure to bring a laptop with your favourite development environment (the current version of PHP, an IDE, and PHPUnit). Attendees should have a good working knowledge of PHP, decent OOP skills, and be familiar with the basics of PHPUnit. No frameworks or other third-party code will be needed.

Was macht sauberen Code aus? Wie wird Code richtig gut? Und wie schreibt man richtig guten Code? In diesem Workshop lernt Ihr das nicht nur, sondern Ihr könnt es auch direkt in die Praxis umsetzen! Zunächst demonstriert Sebastian Bergmann den Einsatz von Domain-Driven Design und Test-Driven Development, natürlich nicht ohne auch über Themen wie Clean Code oder die SOLID-Prinzipien zu sprechen. Danach arbeitet Ihr in Paaren und setzt das Gelernte in die Praxis um. Wir schließen den Tag ab mit einer Review-Runde, in der Ihr Feedback zu Eurem Code bekommt. Um von diesem Workshop wirklich profitieren zu können, bringst Du bitte Dein eigenes Laptop mit Deiner gewohnten Entwicklungsumgebung mit. Neben IDE (oder Texteditor) brauchst Du eine aktuelle Version von PHP und PHPUnit. Frameworks oder Third-Party-Code wird nicht benötigt.