“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.
“I see tons of recommendations *how* to do architectural work better. But at least from what I have seen, none of them asks the *why* question. Architecture and architectural work are declared ‘important’ without any further justification or explanation, just for being what they are. For me, it feels like architectural work has become an end in itself in most places.”
“Teaching a subject like software architecture only goes so far, then apprenticeship or something similar should kick in. Software architectures are too different, and we don’t the formal rigor of other engineering disciplines to allow objective analysis to the degree of more established engineering disciplines. Software architecture still relies on experience to make good trade-off analysis decisions, which is hard to teach.”
In this blog post, Dr Annegret Junker explains how integration architectures are the key to modern applications in hybrid cloud environments or even in mixed hybrid cloud and classic environments.