togaf

Why Architecture Frameworks Matter

by

If there is one statement that has become increasingly common on social media platforms, conference stages, and architecture forums, it is this:
We don’t need architecture frameworks anymore.
Some argue that frameworks are outdated. Others describe them as bureaucratic, heavyweight, or simply incompatible with agile ways of working. According to some, frameworks like the TOGAF® Standard only exist to generate documentation rather than value.
In this blog, I will dive into why architecture frameworks matter.

The post Why Architecture Frameworks Matter appeared first on EAWheel.

Zero-Reload Nginx Upstream Management as an Enterprise Architecture Decision

by

Zero-Reload Nginx Upstream Management as an Enterprise Architecture Decision: A…

The Modern Enterprise Architect

by

There was a time when the Enterprise Architect was easy to identify. They were the ones with the largest diagrams. The most boxes and arrows. The most opinions about standards. They could quote frameworks like scripture and had a sixth sense for spotting an unauthorized integration. If something wasn’t aligned to the target architecture, they knew. And they would tell you. Probably in a steering committee. The modern Enterprise Architect looks very different from the one many organizations designed their structures around.

The post The Modern Enterprise Architect appeared first on EAWheel.

Creating Enterprise And Architecture Principles

by

Within an Enterprise Architecture approach, principles serve as a foundation for designing flexible and scalable architectures that align with business goals and objectives. They ensure compliance with regulations and industry standards and are able to reduce complexity and duplication by enforcing standardization and interoperability.
Principles provide clarity, consistency, and direction in decision-making, ensuring alignment between business objectives and strategies. Evidently, their value lies in ensuring that business and IT strategies support the same objectives. In other words, principles guide strategic alignment.
This hands-on blog will focus on creating Enterprise and Architecture Principles, based on an organizational strategy.

The post Creating Enterprise And Architecture Principles appeared first on EAWheel.

More Practicality, Less Theory

by

Enterprise Architecture frameworks are rarely questioned at the conceptual level. Most architects accept their value. Many organizations reference them explicitly. Certifications remain popular, methods are well known, and the language of architecture has become increasingly standardized across the profession. Yet something interesting happens when these frameworks enter daily practice: the translation becomes challenging, resulting in difficulty gaining stakeholder buy-in. However, stakeholder buy-in is not the issue.

The post More Practicality, Less Theory appeared first on EAWheel.

A Scrapbook of Past Projects

by

Enterprise Architecture has a reputation problem. Not because it lacks rigor or structure — quite the opposite. But because too often, architecture feels like something that exists next to the organization rather than within it. Diagrams live in tools, standards sit in documents, and architectural knowledge slowly fragments across folders, platforms, and people’s heads. It’s kind of like an intangible scrapbook of past projects.
The Architecture Repository, as described in the TOGAF® Standard, is an attempt to fix that. Not by introducing yet another tool or database, but by introducing a way of thinking. A way of treating architecture as a coherent, evolving body of knowledge — one that can be reused, governed, and continuously refined.

The post A Scrapbook of Past Projects appeared first on EAWheel.