Join us at TechEx 2024!

From June 5-6 we'll be at the event series for the tech ecosystem.

Learn more
Back to Insights

May 2, 2024

How our SRE Studio efficiently manages cloud infrastructures

Qubika’s SRE, Cloud, and Cybersecurity Studio share key tools they use to efficiently manage cloud infrastructures.

How our SRE Studio efficiently manages cloud infrastructures

Many businesses today are focusing on managing more effectively their cloud environments, while also working to reduce errors and ensure the performance of their business critical applications. Our SRE, Cloud, and Cybersecurity Studio is at the forefront of these efforts to improve the management of our client’s infrastructure.

We wanted to share here some of the elements the team have been working on- both tools that we’ve developed internally, as well as how we use open source and commercially available tools to best help our clients with their technology environments.

SRE Bootstrapper: Qubika’s tool to rapidly set up new cloud environments and more easily provision network instances

With our SRE Bootstrapper tool we automate the cloud infrastructure setup when we start working with a new client. A typical manual process for setting up the infrastructure, and provisioning the network instances, takes about a day and a half – mixed in of course with the risks of human errors. With the tool, we do it in minutes. Having an automated process means we save a significant amount of time right at the beginning of projects with clients. It also enables us to provision almost everything – instances, networks, secrets, logs, certificates, domains, and scaling, and much more.

We decided to build the tool using Terraform as it enables us to use infrastructure-as-code. In plain English, that means we can simply write the code, “hit play”, and everything is automatically deployed.

We’re already working on the future iterations of Bootstrapper. In particular we want to ensure our teams have significant flexibility to adapt to specific or unique situations. For example, the next iteration will make it easier for us to create multiple environments (production, development, QA, staging etc) with the same infrastructure-as-code configuration.

Tools for developers

Here at Qubika, we focus on building quality software. As part of this, many of our teams take advantage of Sentry, which provides open-source error tracking and performance monitoring.

We have also created a module in Terraform for error monitoring, which sets up alarms on CloudWatch for any AWS hosted system – this provides notifications about aspects such as application downtime, 5XX HTTP errors, and resource utilization. Importantly, it automates the creation of alarms on the infrastructure – this means, for example, that businesses can ensure their customers never get to the point where they experience their system being down. Notifications are sent via email or Slack (or whichever preferred channel) so that the team can take preventive actions.We also use Github Actions to implement continuous integration/ continuous development (CI/CD) pipelines, which then automate things such as running unit tests on code, linter on every merge, automatic image building and compilation, automatic deploys, and much more.

How it works in practice: Bringing it all together for a client

For one of Qubika’s clients we were faced with a situation where they had 3 main repositories. One of these functioned as the base service. This was then used by a microservices application with 9 components. Then there was a third repository which had various deployment tools. To enable the images in the application involved hundreds of lines of sequential code, clearly bringing various problems to their development team.

We identified four main problems:

  1. Multiple manual processes being executed locally.
  2. Missing access control and roles for tasks and processes.
  3. No centralized logs and their execution history was missing.
  4. No notifications for process results.

We achieved the following key objectives:

  • Moved tasks to their corresponding repository, removing unnecessary dependencies between them.
  • Implemented build and push image automation.
  • Reduced the build time via parallel execution and cache.
  • Set up of notifications for build release process results – this also solved the issue of the execution history.

Conclusion

The tools that our SRE Studio has created, and also those they have evaluated, enable all teams at Qubika to provide a best in class service to our clients, and manage their cloud environments effectively.

Interested in learning more about Qubika’s SRE, Cloud, and Cybersecurity Studio and the work it does? Then check out https://qubika.com/studio/sre-cloud-cybersecurity/

juan andres zeni

By Juan Andrés Zeni

SRE Studio Manager

Juan Andres is the SRE Studio Lead at Qubika, where he works in the design and implementation of fault-tolerant, cost-efficient, and resilient architectures in the cloud for agile software projects.

News and things that inspire us

Receive regular updates about our latest work

Let’s work together

Get in touch with our experts to review your idea or product, and discuss options for the best approach

Get in touch