Technical Architectural Diagram, but pretty

Tecnología

run_as_root is an eCommerce software development agency based in Germany. We are specialized in Magento 2 and individual software development with PHP.

We recently created an architectural diagram that shows the process of how data from different services results in incidents. This diagram is quite ugly, so we need a designer helping us to prettify it. The diagram itself should be self-explaining. I will attach the diagram. Feel free to rearrange the items in the diagram as long as the connections make sense. Some information about the content of the diagram follows: The diagram itself describes the connections between the data that can occur on different systems. For example, when running an eCommerce Site, you will be confronted with a lot of different data. Data is coming from services like the Database (MySQL), the specific Shop itself or any other technical services. Services(basically Data Sources) can vary from project to project. This huge amount of data is necessary for the development team to analyze or reproduce bugs. Nevertheless, most of the data is useless in its raw format. Therefore we need the Aggregator Phase that receives the data and prepares it, so it can be used by others. Having aggregated data is fine, but this data is still too much to handle by a person. Therefore we have to add a service that is able to evaluate rules. Based on these rules, incidents can be triggered. This is done by the incident management which takes care of informing the development team. An incident management system takes care of calling the right person for the issue. If a database issue occurs, the incident management knows who to call for this kind of problem. As there are a couple of services, the development team would be overwhelmed by the number of services. Therefore specific important services like Grafana or Sentry are integrated into GitLab. GitLab is the version control system and is the single point of touch for the development team. Regarding the style of the diagram. We like to have it isometric. As it is a technical drawing, we like it to be minimalistic and clean. We like the following styles: - https://dribbble.com/shots/8930575-WeWork-Main-Illustration - https://dribbble.com/shots/4958999-Creating-a-Design-System - https://dribbble.com/shots/8072458-Future-Tech-Business The result should look similar to a diagram made with https://cloudcraft.co/ but better styled.

Toda categoría de diseño tiene precios flexibles para todos los presupuestos. Gráficos e Ilustraciones comienza en $349.