Blog iSAQB Software Architecture Gathering 2025? Manfred Steyer Google Developer Expert focusing on Angular Published on September 29, 2022 Module Federation: The Game Changer for Micro-Frontends An interview with Manfred Steyer by Richard Wallintin In anticipation of Manfred Steyer’s session,
Blog iSAQB Software Architecture Gathering 2025? Sander Hoogendoorn Tools do not solve problems, thinking does. Published on September 28, 2022 Small Steps, Collectives and Failure in Software Development An interview with Sander Hoogendoorn by Richard Wallintin In anticipation of Sander Hoogendoorn’s session,
Blog iSAQB Software Architecture Gathering 2025? Jeff Sussna Director of Technical Agility, Cprime Published on September 21, 2022 Team Topologies-Influenced Architecture An interview with Jeff Sussna by Eberhard Wolff In anticipation of Jeff Sussna’s keynote,
In this talk, Chris Richardson describes loose coupling and modularity and why they are essential. You will learn about three architectural patterns: traditional monolith, modular monolith and microservices. I describe the benefits, drawbacks and issues of each pattern and how well it supports rapid, reliable, frequent and sustainable development.
In this talk, Kevlin Henney looks at the relationship of knowledge to software, the codification of knowledge in architecture, the acquisition of knowledge to development process, and how we can make progress in the presence of known unknowns, unknown unknowns and unknowable unknowns.
Software Architecture is about the important things, where “important” means high-risk and hard-to-change decisions. DevOps tries to develop a culture where constant experimentation and learning takes place while the environment changes rapidly. How can this fit together?
We have been building software systems for over sixty years, and they continue to grow in size and complexity. Many of them have become large obscure tangles of legacy code that drives up development costs. Is this inevitable? What can we do to get our Legacy in good shape and keep it that way?
We see a lot of confusion regarding architectural work these days. When? How much? Who? Tons of heated debates and nobody asking the essential question: Why? But without asking Why, all the other questions are futile. Thus, we will start this session by asking: *Why* do we need architectural work? And which problem(s) does it address?
“For a DevOps team, one of the main goals is to provide continuous delivery of value for end users. As a result, you’re working as a team in small increments and try to deliver new features to production as soon and often as possible, and get as much feedback as you can along the way. When a team is moving at such a fast pace, continuously adding new features and refining existing ones, it can be difficult for a software architect to keep up.”
In his upcoming session “Domain-Driven Design & Legacy: Evolution not Revolution” Eberhard Wolff, will look at how to improve your legacy systems using Domain-Driven Design. We sat down with him to ask him a little about the topic.
Sponsoring a conference is a terrific way to support and connect with our global community of software architects.
You need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from Turnstile to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Google Maps. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information