IaC (Infrastructure as Code)
This is an approach that we implement every day. Why? Because it enables the implementation of true DevOps; opens the gates to Continuous Deployment and Blue-Green Deployment. We like to weave linters and tools for static code analysis into pipelines, also from a security perspective, to make room between Dev and Ops also for Sec.
What does our communication look like? We won’t reveal the team’s secret, but we can say that the front end often talks to the back end with the help of GraphQL. We find particular pleasure in using subscriptions, as they allow us to achieve a special harmony between the front end and the back end.
We like diversity and polyglot persistence – for different types of conditions and challenges, we carefully select programming languages and technological tools. We adapt databases to the microservice, or going even further, sometimes to a specific use case. We have no scruples about keeping data in either relational or document databases. We are not afraid to keep data in an event store or in files, but we do not want to be brave like that blind horse – we choose tools to efficiently overcome
obstacles rather than crash into them.