EN 
NL What is Solution Architecture?
Solution architecture in this context refers to the idea of putting the architecture in direct connection with the business problems in order to create an effective and scalable solution. Within the integration domain, it is important to create a solid foundation with which to shape the connectivity to the systems or APIs to be integrated and the translation of the desired properties of these integrations. This must take into account, for example, the frequency and size of the data packets exchanged through the various integration patterns.
The visual aspect of a solution architecture is important so that there is a unified view for business and IT about how the integration components will be distributed and exactly where they will need to run. The properties of the solution will need to be unambiguously defined and should be available to those who actually need to implement the integration.
Solution Architecture in eMagiz
Within the context of eMagiz, the term "Solution Architecture" refers to how the various software components are distributed across the eMagiz Cloud and across the client infrastructure. In these software components run the parts of an integration that allow, step by step, the integration to work from source to target. From a business point of view, it is possible to keep the source and target systemsand that consume or produce data independent of each other in the integration architecture. This creates sufficient independence in the landscape considering release management, guaranteed delivery or data packages and limiting the impact of downtime.
Design and Deploy architecture in eMagiz
Het iPaaS van eMagiz maakt Solution Architecture concreet door een Design Architectuur te presenteren. Hierin visualiseer je de benodigde systemen die data consumeren of produceren, en verdeel je deze over eMagiz Cloud of klantinfrastructuur. De Design Architectuur biedt directe berekeningen, zoals T-shirt sizing, om de omgevingen in te richten voor test-, acceptatie- en productieomgevingen.
Separating Design and Deploy Architecture is crucial to validate the architecture before deploying integrations. The Deploy Architecture executes the Design Architecture over the AWS Cloud, updating cloud instances automatically. The calculated memory setting can then still be changed, if deemed necessary by the architect. All the settings needed to manage the Cloud environment are present - allowing the user to manage the environment independently of other teams at the client.
Key benefits of Solution Architecture in eMagiz
- Visual Design: eMagiz allows architects to create visual design for the integration architecture, creating a unified view across different environments.
- Simple Implementation: At the touch of a button, eMagiz can fully effectuate the desired Solution Architecture over the Cloud. No complex deployments are required and you do not need any specific technical knowledge for your Cloud Formation.
- Architecture principles: eMagiz takes into account important architectural principles, such as separation of concerns and fail-over, to ensure a stable and constant integration environment.
In the integration domain, Solution Architecture represents the crucial link between technical aspects and business issues. Its foundation requires careful planning and visualization to provide effective, scalable solutions. It is therefore one of the key features within eMagiz to achieve optimized and reliable integration environments. Would you like to learn more about the rationale behind Solution Architecture or have a conversation with us? Feel free to contact us.
Solution architecture uitgelegd:
Would you like to learn more about the other features of the eMagiz iPaaS? Then take a look at:
