{"id":12263,"date":"2023-03-15T12:27:17","date_gmt":"2023-03-15T11:27:17","guid":{"rendered":"https:\/\/symmedia.de\/en\/?p=12263"},"modified":"2023-10-16T10:43:12","modified_gmt":"2023-10-16T08:43:12","slug":"business-driven-solution-architecture","status":"publish","type":"post","link":"https:\/\/symmedia.de\/de\/business-driven-solution-architecture\/","title":{"rendered":"Business Driven Solution Architecture"},"content":{"rendered":"
\n<\/div>\n
\n<\/div>\n
\n

In this symZone article, I would like to invite you to take a quick look behind the scenes of Secure Service Hub (SSH)<\/strong> and show you how we develop the perfect application architecture for ever-growing (business) demands to modern software solutions like SSH<\/strong>. For us, the decisive success factor is the consistent alignment of the software architecture with the business model and the associated value proposition. This is neither a new software design pattern, nor does it replace valuable and meaningful patterns such as BDD or DDD (Behavior\/Domain Driven Design), which we also use. Rather, it is a philosophy that we have embedded throughout the organization and to which everyone is committed.<\/p>\n<\/div>\n

\n

Technology is never an end in itself<\/p>\n<\/h2>\n

\n

Technology is fun, challenging and motivating at the same time, but should never become an end in itself. The increasingly shorter cycles in which new concepts of software architecture, frameworks and tailored programming languages appear on the market lead to an increasingly complex landscape of solutions. If you look at the different options relatively encapsulated and in the context of successful application cases, they are usually always valid and value-adding. The great danger lies in the use of concepts and technologies for reasons such as good experience in previous projects, existing know-how in the company or current hype in the market without considering the most important aspect \u2013 the business impact.<\/p>\n

In today’s world, it is no longer the technological hurdles that define the limits of what is possible – almost any functionality imaginable can be implemented with appropriate technologies such as AI, blockchain or virtual reality. BUT: It is the view of the business model, customers, industry, etc. and the requirements derived from them that should have a decisive influence on the architecture and technologies used in a solution.<\/p>\n<\/div>\n

\n

Business First-Thinking<\/p>\n<\/h2>\n

\n

So, we must avoid designing technology-driven solutions, as it unfortunately happens in many cases, regardless of how much experience the development team has or in which domain the solution is to be deployed. When designing and implementing Secure Service Hub<\/strong>, we were guided by a \u201cBusiness First\u201d approach.<\/p>\n<\/p>\n

Let me explain this approach using three selected value propositions that we want to offer our customers with SSH<\/strong>:<\/p>\n