What is the core of Azure?

Why do we care what is the core of Azure?

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.

Key Azure Components
Abstract shapes or Key Azure Components?

Continue reading “What is the core of Azure?”

Enterprise Architect vs Solution Architect

Mask of Happines

(Update: To illustrate the “knot-weed of legacy and errors” that can grow out of fertile misunderstandings of architectural roles in a real-life organization, perhaps this might be one sobering example. Reading this amazing job description, one might think, for a single person, even “Neo” has no that much powers, as they ask from a poor architect.)

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.

Continue reading “Enterprise Architect vs Solution Architect”