In the second part of their article, Vasile Buciuman-Coman and Michael Chervenic explore the architecture of Dynamic Business Application after having defined a new Enterprise Framework in Part I.
there is a fundamental difference between architecting software applications and designing other engineered products. Because software works with information, and information is the “carrier” for change, then change has to be built into the system architecture at the most basic level.
The core of the proposed solution is based on two frameworks:
These two frameworks allow us to handle and coordinate changes in business operations and technical team operations effectively and efficiently. For the design process, business operations and technical team operations can be considered two distinct adaptive systems, each with their own requirements.
The authors note that:
...architecting a client-server application capable to run at the enterprise level is orders of magnitude more complex than a desktop application. The main complexity of the server-side application derives from the fact the it must support two adaptive systems, one for the technical team and one for the business team, each with their own operations and controlled hierarchy.
The architecture style of Dynamic Business Applications (dubbed Adaptive Enterprise Operating Platform -AEOP) is focused on productivity for the technical team operations, the business operations and the development team. Increased levels of productivity are reached through an entity lifecycle/event-based architecture style. However,
the EDA (Event Driven Architecture) model found in the literature is different than the AEOP event model. The EDA is built around a stream of unstructured events, while the AEOP is built around a stream of structured events that are linked together by a clear set of lifecycle templates.
After describing in great details the architecture of Dynamic Business Applications, the authors conclude:
AEOP standardizes the architecture for server-side applications, something that is missing from current IT
Technologies and architecture concepts like SOA play a minor role in this architecture. Components like BPM engines, schedulers, messaging have a clear role in this architecture, however they have very little impact on the design.
/filters:no_upscale()/sponsorship/topic/2c0d72d2-1768-47c2-8f5b-24f3ef0ae0e0/QconNYrsb-1679560094156.png)
/articles/rapid-startup-of-your-cloud-native-java/en/smallimage/logo-1680293937095.jpg){kind=logo}
/minibooks/architecture-2023/en/smallimage/logo-1685600892155.jpg){kind=logo}
/articles/architecture-modernization-domain-driven-discovery/en/smallimage/start-your-architecture-modernization-with-domain-driven-discovery-small-1683106490819.jpg)
/articles/api-design-review/en/smallimage/API-design-reviews-are-dead-long-live-API-design-reviews-small-1684310900854.jpg)
/articles/agility-architecture/en/smallimage/logo-1682078942739.jpg){kind=logo}
/articles/architecture-trends-2023/en/smallimage/the-infoq-trends-report-1680611416202.jpeg)
/articles/framework-architectural-decisions/en/smallimage/logo-1679060242842.jpg){kind=logo}
/articles/istio-ambient-mesh/en/smallimage/logo-1678364642232.jpg){kind=logo}
/articles/effective-architecture-conversations/en/smallimage/have-effective-conversations-with-business-stakeholders-about-software-architecture-small-1677231728391.jpg)
/articles/creating-decentralized-apps/en/smallimage/LOGO-1676916574942.jpg){kind=logo}
/presentations/data-streams-architecture/en/smallimage/Kai_Waehner-s-1675025271514.jpg)
/articles/architecture-skeptics-guide/en/smallimage/a-skeptics-guide-to-software-architecture-decisions-small-1672223516348.jpg)
/minibooks/2022-infoq-trends-reports/en/smallimage/LOGO-1672051527011.jpg){kind=logo}
/presentations/ddd-team-topology/en/smallimage/Nick Tune-s-1675667798480.jpg)
/articles/how-to-manage-full-stack-java-development-with-hilla/en/smallimage/manage-full-stack-java-development-with-hilla-small-1686055303315.jpg)
/articles/debugging-beneath-trusted-abstraction/en/smallimage/debugging-outside-comfort-zone-diving-beneath-trusted-abstraction-small-1685961994992.jpg)
/articles/delivering-fast-testing-strategies/en/smallimage/deliver-fast-tests-have-to-last-small-1685548178496.jpg)
/articles/eda-mediator/en/smallimage/event-driven-architecture-with-mediator-topology-small-1685547200315.jpg)
/articles/azure-functions-quarkus/en/smallimage/azure-functions-on-quarkus-3-1685542580748.jpg)
/presentations/lyft-cd-benefits-challenges/en/smallimage/tom-wanielista-small-1685002834068.jpg)
/presentations/green-software-growth/en/smallimage/Marco-Valtas-small-1685609473905.jpg)
Community comments
Interview with Grady Booch and the software's "dirty little secret"
by Vasile Coman,
Very interesting ideas
by Harmen Dijkstra,
Interview with Grady Booch and the software's "dirty little secret"
by Vasile Coman,
Your message is awaiting moderation. Thank you for participating in the discussion.
Here is an interesting quote from an interview Grady Booch gave to Scientific American about software few days ago (June 17, 2008)
Software's Dirty Little Secret - An interview with Grady Booch, the Indiana Jones of computer programming
:
"Q:You say there's a "dirty little secret" when it comes to writing software. Care to share that with us?"
"A: <quote> In other disciplines, engineering in particular, there exist treatises on architecture. This is not the current case in software, which has evolved organically over only the past few decades. All software-intensive systems have an architecture, but most of the time it's accidental, not intentional. This has led to the condition of most software programming knowledge being tribal and existing more in the heads of its programmers than in some reference manual or publicly available resource.</quote>"
Very interesting ideas
by Harmen Dijkstra,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi, I've read both papers last weekend and must say that you propose some very interesting concrete approaches to deliver on the contents of the DBA paper by Forrester. I'm eagerly awaiting part three where you promise to describe a practical implementation, as I do have some doubts as to how the containers are implemented technology wise.
Harmen