This presentation by Maciej Jedrzejewski explores the concept of evolutionary software architecture, arguing that architecture is not a static, upfront design but a continuous process. It delves into the cognitive biases that lead to over-engineering, emphasizes the critical role of context, and provides a practical four-step model for evolving systems from simplicity to complexity.
A panel discussion with Spring Framework creator Rod Johnson and veteran Arjen Poutsma, moderated by Trisha Gee. They discuss the evolution of Spring, the future of reactive programming in the age of virtual threads, their new AI agent framework Embabel, and the essential AI skills modern Java developers need to acquire.
CircleCI's Olaf Molenveld and AWS's Julian Wood explore the evolution of CI/CD, drawing parallels between managing production code and the 'factory' that builds it. They cover the shift to microservices pipelines, optimization strategies, platform engineering trends, and how AI is set to reshape DevOps by acting as an expert system for developers.
Authors Martin Štefanko and Jan Martiška discuss their book "Quarkus in Action," detailing the framework's powerful developer experience, the trade-offs between JVM and native compilation, and its cloud-native capabilities. They explore the book's structure, which guides readers through building a complex microservices application to showcase over 29 different extensions, from REST and gRPC to reactive messaging and cloud deployment.
Olaf Molenveld (CircleCI) and Julian Wood (AWS) discuss the evolution of CI/CD practices. They draw parallels between managing production code and the 'factory' that produces it, covering optimization strategies, local vs. remote development, the rise of platform engineering, and how AI is reshaping DevOps by acting as both an expert system and a guarded collaborator.
Legacy code isn't just old; it's a treasure trove of lost business knowledge. Alessandro Colla and Alberto Acerbis, authors of 'Domain-Driven Refactoring,' argue for a business-first approach to modernization. They explain how to rediscover the 'why' behind your system using Domain-Driven Design, treating the monolith not as something to be destroyed, but as a block of marble from which a well-structured solution can be carefully carved.