Category: Architecture. A formal description of the system
Architecture is a formal description of the system. Also of components of which system is made. In every modern enterprise, IT Architectural roles are wide and varied. Most importantly, here you might gain some useful insight into the creation of architectures for all sizes of businesses, systems, technologies and software too.
By no means do not hesitate to leave comments. In case the nature of your contact request is commercial please do mail us using email@example.com
Here is why. It seems Microsoft marketing has overwhelmed the target audience with dozens of made to be equally important Azure “services” (for the lack of better word). The “full Monty”: Posters, charts and animations. It is enough for Azure newcomer (developer or decision maker) to make and keep her dizzy, instead of producing focused and relaxed visitor, when entering the Azure yonder.
(Update: To illustrate the “knot-weed ” that can grow out of fertile misunderstandings of architectural roles in a real-life organization, perhaps this might be one sobering example. One might think, for a single person, even “Neo” has no that much powers.)
One question is often asked, at least into my direction. What is the actual difference between Enterprise Architect and Solution Architect?
First of all, there are much more roles for Architects in any modern business. But let’s answer that later. To help the understanding of the audience I often use the following analogy:
The Enterprise Architect is like a town planner. Solution Architect is designing the buildings in that town.
Thus Solution Architecture starts inside the boundaries defined by enterprise architecture.
With my TOGAF hat on, I would say: Top level Architecture continuum of an organization is defined by Enteprise Architecture. Principles and Artefacts and Reusable Blocks.
But it might contain some pieces of information that might come handy to more than few CxO ‘s right now. Especially if the said CxO ‘sare given the responsibility to “own” the IT landscape in some medium or large organization. Approx 50 seats onward, complexity depending.
In this context, and perhaps because of this post, I might be called a bit of a pessimist., which is calling himself a realist.
Side note: Perhaps looking for good copy/paste opportunity? Click here for your required dose.