Software Architektur im Stream

Am Ende des letzten Jahrhunderts stand Wiederverwendung im Mittelpunkt des Interesses: Dadurch sollte Software-Entwicklung endlich einfach und unfassbar produktiv werden. Nun sind mehr als zwanzig Jahre vergangen und es scheint auf den ersten Blick so, dass Wiederverwendung doch kein erfolgreiches Konzept war. In dieser Episode sprechen wir darüber, was wir in den letzten zwanzig Jahren gelernt haben - und wie Wiederverwendung in aktuellen Projekten stattfinden kann und sollte. Umweltamt zu Plastik-Recycling Nachricht zu Plastik-Recycling San Francisco in 2005 neu starten? Paper Object Oriented Application Frameworks the Untold Story Blog: Die Cloud - Eine Komponentenbibliothek

Nachdem es schon einige Folgen zum Thema Frontendarchitektur gab, die eher den Fokus auf Server-seitig gerenderte Architekturen gelegt haben, gibt es nun endlich eine Episode mit Manfred Steyer, die den Fokus auf Single Page Applications legt. Wir sprechen über Modularisierungskonzepte dieser Art von Architektur, wie zum Beispiel Microfrontends und Clients-Modulithen. Außerdem zeigen wir euch Entscheidungshilfen für die Wahl des passenden Konzepts und vieles mehr. Manfreds Blog

Written self-reflection is very powerful and - at the same time - it is still quite rarely used in the business context. Cosima talks with Lisa about why this is the case and what can be done to improve the situation. Link collection links to worksheets, InfoQ.com article on ‘How Journaling puts Leadership in ACTion’, a podcast (in German), and various other related resources

Organisation und communication have a huge impact on software desgin and architecture. Avraham Poupko and Kenny Baas-Schwegler take this a step further and talk about the influence of culture on software design. Links Book: The Corporate Tribe: Organizational lessons from anthropology Book: Team Topologies: Organizing Business and Technology Teams for Fast Flow

Code is read more often than written. Felienne Hermans talks about how to read complex code with Lisa Moritz and the book she wrote about this topic. Links Get 35% discount on Felienne’s ebook “The Programmer’s Brain” at Manning with the code podsoftarktv21 Code Reading Clubs Website Felienne’s Homepage

James Lewis is one of the microservices pioneers. We talk about when to use microservices and the organizational side of microservices e.g. the inverse Conway maneuver. Lately, James became interested in flow. Links Talk Java the Unix Way Video Slides Java the Unix Way Video Microservices article by James Lewis and Martin Fowler

Software architecture is fundamentally about how to split a software system into multiple parts. In this episode, we discuss this basic challenge: We talk about modularization with approaches like microservices and monoliths with Chris Richardson. Chris is a Java Champion and a Java One rock star. Nowadays, he works on microservices with his web site microservices.io and his book “Microservices Patterns”. Links microservices.io eventuate Chris’ microservices book Team Topologies Book Accelerate Book

Software architects are faced with uncertainty more often than we like to admit. How can we deal with it - or can we even make it disappear? In this episode, we will talk about uncertainty with Kevlin Henney. He has been a member of the IEEE Software Advisory Board, coauthor of several books on patterns, editor of 97 Things Every Programmer Should Know, and co-editor 97 Things Every Java Programmer Should Know. Links Phillip G. Armour: The Five Orders of Ignorance Planning Fallacy Adam Tornhill: Your Code As a Crime Scene: Use Forensic Techniques to Arrest Defects, Bottlenecks, and Bad Design in Your Programs Software Architecture Gathering Registration discount code SAG21_EW_15 for 15% off

The architecture of a system has to change over time. In this episode, we will discuss evolutionary architecture and why it is important. We will talk about patterns and principles to build architectures that stand the test of time. Dr Rebecca Parsons co-authored of a book about evolutionary architecture and has extensive experience with application development. Before becoming the CTO for Thoughtworks, she worked as an assistant professor at the University of Central Florida and as Director’s Post Doctoral Fellow at Los Alamos National Laboratory. Scott W. Ambler , Pramod J. Sadalage: Refactoring Databases: Evolutionary Database Design: Evolutionary Database Design Software Architecture Gathering Registration discount code SAG21_EW_15 for 15% off

Lose Kopplung stellt eine grundlegende Eigenschaft eines modularen Systems dar. Sie soll Änderungen vereinfachen, indem jede Änderung nur einen begrenzten Teil eines Systems beeinflusst. Obwohl der Begriff so wichtig ist, gibt es gerade in diesem Bereich immer wieder Missverständnisse. In dieser Episode diskutiert Eberhard Wolff die Bedeutung des Begriff und warum lose Kopplung so wichtig für Software-Systeme ist. Außerdem spricht er über verschiedene Ansätze, um lose Kopplung tatsächlich zu erreichen. Links Wikipedia zu Loose Coupling Wikipedia zum Robustheitsgrundsatz / Gesetz von Postel Kafka Video