Architecture services

Why do I need architecture or architects? What’s the actual benefit ? What is architecture actually contributing to my bottom line ? Isn’t this just another cost with intangible ‘benefits’? The former questions occasionally come up in medium or large organizations, that tend to have very broad definitions of architecture and roles. While definitions of Architecture can be very broad, what we refer to with architecture is:

• Solution, Integration, Enterprise, -Architecture.

Since we also develop and implement solutions we have the ability to overlook the relevant architecture(s) from top to down as well as bottom up. This helps us in making sure you get real value, e.g. actionable designs/plans that ‘fit’ your business needs as well as your legacy systems. We provide all flavors of architecture, whether it be technical low-level integration patterns or Enterprise architecture decisions. All in our no-nonsense, straight to the point fashion. Reach out, and find out how architecture can be a real value add, and not a brake on your IT and business. To help cut through the buzzword salad, here are some quick summaries of what we consider under which architecture definition; (*note: These are all just ‘a’ definition. I’ve heard and seen as many different definitions of these terms as there are companies).

Solution architecture

A relatively ‘low level’ technical design of the functionality that is needed within the context of the systems that are supposed to deliver it. Hence it provides an overview of the ‘how’ the system is to provide the relevant functionality. The output from a quality solution architecture can directly be implemented. Either locally, or by a (near shore) partner. Due to the standardized modeling languages / schematics.
What we do: Create the necessary solutions architecture, that seamlessly integrates with your existing system(s). Ready for implementation, and we can develop the implementation from there on.

Integration architecture

Refers to the patterns, and systems of integration between systems either in your domain or outside of it. Due to the cost of certain systems and the required effort to implement one or the other, it tends to become an ‘organizational wide’ choice. Which often results in relatively sluggish implementation, and equally cumbersome modification of the chosen architecture down the road. Since we provide various integration services we like to adopt a flexible integration solution whenever possible. The downside of flexibility is usually more complexity, cost or both. Depending on your chosen solution. E.g. more technical vs. a well packaged API management solution.
What we do: Help you make sense of the seemingly endless options of patterns, systems and vendors providing a clear overview of the pros and cons. As well as support for the implementation.

Enterprise architecture

Generally the most glamorous of all architects. I consider it the overlay of the technical domain with the business goals and processes. Your enterprise architecture should capture the: "What, how and why" of how your IT landscape will aid the organization in reaching it's business goals. And a high level overview of the major systems and components that comprise the machinery behind it. While it is a key component in virtually every modern organization, unfortunately more often than not it's not a success. Due to a myriad of reasons. The enterprise architect (EA) position requires a vision toward the future of the marketplace as well as the trajectory the industry is on. Without falling victim to hype-think.
What we do: Assess, what is working and what is not. Setup necessary elements of a resilient and future proof enterprise architecture together with relevant architectural processes.

Concluding remarks

Hopefully this sheds a bit of light on the different definitions, and what we can do for you. As always we strive to make our contribution practical and tangible. In the shortest time possible.