{"id":17636,"date":"2025-03-07T17:09:57","date_gmt":"2025-03-07T16:09:57","guid":{"rendered":"https:\/\/immune.institute\/?post_type=proyecto&p=17636"},"modified":"2025-10-07T10:51:03","modified_gmt":"2025-10-07T08:51:03","slug":"automatizacion-base-acelerar-desarrollo","status":"publish","type":"proyectos","link":"https:\/\/immune.institute\/en\/proyectos\/automatizacion-base-acelerar-desarrollo\/","title":{"rendered":"Automation as a basis for accelerating the development lifecycle"},"content":{"rendered":"
\n
\n

Within cloud working, automation is one of the most important key elements, as it facilitates consistent and reliable results. <\/p>\n\n\n\n

The standardisation achieved through this automation allows for the optimisation of resources, which can be very limited, and the adoption of best practices that improve operational efficiency.<\/p>\n<\/div>\n\n\n\n

\n

Carried out by<\/mark><\/strong> Jos\u00e9 A. Melgar<\/a> | Sergio Pardo<\/a> | Alejandro Lizar\u00e1n<\/a><\/p>\n\n\n\n

Qualification<\/strong> Bootcamp on DevOps and Cloud Computing<\/a><\/p>\n\n\n\n

Technologies<\/strong> Azure DevOps | Terraform | Entity Framework Core | SQL | Enter ID<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n

What is the motivation? <\/h2>\n\n\n\n

Cloud environments offer great potential, but often it's not fully exploited. The automation <\/strong>help reduce human errors and ensure more reliable results. When used correctly, these environments strengthen business resilience by protecting critical data and ensuring its integrity and availability.<\/p>\n\n\n\n

Program aims <\/h3>\n\n\n\n
    \n
  • Design a Disaster Recovery architecture<\/strong> Active-passive setup between Azure and GCP that is scalable and fault-tolerant.<\/li>\n\n\n\n
  • Achieve a Recovery Time Objective (RTO) of 30 minutes<\/strong> for critical business infrastructure and resources.<\/li>\n\n\n\n
  • Achieve a Recovery Point Objective (RPO) of 30 minutes<\/strong> for the business database.<\/li>\n\n\n\n
  • Design an automated deployment and management strategy<\/strong>.<\/li>\n<\/ul>\n<\/div>\n\n\n\n
    \n

    Development <\/h2>\n\n\n\n

    The development of this solution for disasters affecting critical infrastructure has moved away from the usual practice of using native resources offered by cloud providers and has focused on non-native migration tools. The implementation of the solution has been based on: <\/p>\n\n\n\n

      \n
    • Security measures<\/strong>are one of the key factors for a resilient structure. The first major group of measures is related to data security, such as automating database backups with DevOps. In case a security breach does occur, the second group of measures, dedicated to the implementation of an action protocol, is focused on achieving a fast and efficient recovery of the service in case of interruption.<\/li>\n\n\n\n
    • Pipeline in Azure DevOps<\/strong>This approach allowed the deployment of the infrastructure, but also the configuration and automation of the backups, allowing them to be transferred from Azure (active environment) to FCP.<\/li>\n\n\n\n
    • Deployment of the architecture<\/strong>This type of deployment requires more basic tools, such as Visual Studio Code, but also more specialised tools, such as Terraform, which allow working with Infrastructure as Code (IaC). Tools from Google Cloud and Azure, such as Kubernetes, were also used to help in the design, deployment and management process. <\/li>\n\n\n\n
    • Scenario planning<\/strong>In order to anticipate unforeseen events, a multitude of scenarios were considered. They were divided into natural, technical and human, each with a range of possible events leading to service interruption and data loss, such as cloud provider failure or accidental data corruption. <\/li>\n\n\n\n
    • Creating a recovery plan<\/strong>Once an event occurs, a rapid response is necessary to minimise possible damage. To this end, processes such as healthchecks and SQL database backups were automated. The plan itself also needs to be reviewed, so periodic testing was carried out, and different performance metrics and success criteria were established.<\/li>\n<\/ul>\n\n\n\n
      \"\"<\/figure>\n<\/div>\n\n\n\n
      \n

      Results <\/h2>\n<\/div>\n\n\n\n

      The project successfully automated the periodic transfer of Azure backups to GCP, overcoming several challenges and reducing costs by centralising storage in a single bucket.<\/p>\n\n\n\n

      The benefits the project brings to an organisation are:<\/p>\n\n\n\n

        \n
      • Automation of the entire process through pipelines.<\/li>\n\n\n\n
      • Low economic cost for project implementation, because at any given time only the cost of the infrastructure that is in operation is borne, as only one backup storage bucket is deployed in the passive cloud.<\/li>\n\n\n\n
      • Future scalability, requiring further security development phases.<\/li>\n<\/ul>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
        \n

        Conclusions<\/h2>\n\n\n\n

        This project demonstrated a distinct alternative to the usual cloud provider solutions for implementing a disaster recovery system that guarantees business continuity and the protection of critical data. <\/p>\n\n\n\n

        Thanks to the use of Terraform, Azure DevOps, and Kubernetes, Infrastructure as Code was automated, facilitating deployment and management, while database security was strengthened through the automation of backups with pipelines, ensuring their protection and recovery in case of disaster.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

        Automation is crucial within the cloud environment, as it plays a key role in obtaining consistent and reliable results. Adopting this practice allows for the standardisation of processes and limited resources, embracing good practices to improve operational efficiency.<\/p>","protected":false},"featured_media":17647,"menu_order":0,"template":"","area":[242],"class_list":["post-17636","proyectos","type-proyectos","status-publish","has-post-thumbnail","hentry","area-cloud-computing"],"acf":[],"_links":{"self":[{"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/proyectos\/17636","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/proyectos"}],"about":[{"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/types\/proyectos"}],"version-history":[{"count":0,"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/proyectos\/17636\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/media\/17647"}],"wp:attachment":[{"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/media?parent=17636"}],"wp:term":[{"taxonomy":"area","embeddable":true,"href":"https:\/\/immune.institute\/en\/wp-json\/wp\/v2\/area?post=17636"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}