For 160 million years, dinosaurs ruled the world. Then, pretty quickly, and with very few exceptions, they became extinct. Surely, there is something to learn here that will help us to improve the architecture of our software systems. We will approximate the topic by trying to answer two pivotal questions: what would Charles Darwin say about microservices? And: is COBOL still relevant?

Before the start of development comes the gathering of requirements. This daunting task with the seemingly endless discussions. Followed by the creation of epics, user stories or tickets which will change over and over again - even when development has already begun. We can do better than this: With Event Storming, an unlimited modeling space and all the key stakeholder in the same room. Let’s get started with efficient Domain-Driven Design!

Performance is a key success factor for web shops. Over the years, we have gotten pretty good at delivering mostly static content, usually through a combination of heavy caching and the use reverse proxies. Delivering a highly personalized shopping experience, however, is a different beast. This talk goes in depth on how personalization challenges established best practices to speed up web shops, and shows how applying CQRS ideas can help us solve the problem.

Developers need tools to be productive. In this session, Sebastian Bergmann presents an overview of the tools every PHP developer needs to know. For instance, we will have a look at dephpend, php-cs-fixer, phpstan, phan, and PHPUnit. Tools are not an end unto themselves, though. Therefore we will also discuss how these tools fit into your development process.

Entgegen landläufiger Meinung ist kein Code untestbar. Sicherlich macht es mehr Spass, Unit Tests für sauberen, nach SOLID-Prinzipien erstellten Code zu schreiben. Aber was ist mit Legacy Code, der mit zahlreichen Abhängigkeiten aufwartet und sich nicht um die Trennung der Verantwortlichkeiten schert? Sebastian Bergmann zeigt, dass es möglich ist, Tests selbst für den miserabelsten Code zu schreiben. Anhand von Beispielen aus der Praxis zeigt er das Warum, Was, Wie und Wann des Testens von Software.

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.

Die richtige Software entwickeln. Das Richtige testen. Zum richtigen Zeitpunkt. Mit dem passenden Werkzeug sowie den richtigen Kniffen, wie man es effektiv und effizient einsetzt. In diesem Vortrag gehen wir unter anderem den folgenden Fragen nach: Was will ich testen? In welchem Rahmen muss ich es testen? Wie formuliere ich den Test?