Enterprise Architecture Blueprint for Utilities Part 1

Enterprise Architecture Blueprint for Utilities – Part 1:
Technology, Dev Tales,

“The Good, The Bad and the Ugly”

Some days ago, I was co-hosting a webinar on “Piecing together the Enterprise Architecture Puzzle for Utilities”. During our virtual roundtable, our guests including Klaus Wagner, (Enterprise Architect, Netze-BW / EnBW) and Rinse Veltmann (Director Solutions, Energyworx) discussed an enterprise architecture blueprint for the Utility 4.0 future and highlighted specific related topics including:


Challenges or shortcomings with this kind of an “Accidental IT”, that is quite often the As-Is architecture for many utilities.
Strategies such as “Make vs Buy”, “Cloud vs. Data Center”, “Best-of-Breed vs. 1-Stop-Shop” or “Pull IT vs. Push IT”.
Principles and concepts like Event Driven Architecture (EDA), API-driven development, domain driven design (DDD), cloud native, microservices and data mesh.


Our lively debate, in which the panelist shared their views on what was good and bad architecture emphasized: What characterizes a good or bad architecture? What does “good” and “bad” mean? Does “good”, “bad” and even “ugly” mean the same for all of us? And can we measure it? See it? Feel it? Or otherwise sense it?

So let me start by sharing some of the typical indicators and symptoms of a bad architecture from my point of ...


Read More on Datafloq