{"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

Los entornos cloud ofrecen un gran potencial, pero muchas veces no se aprovecha por completo. La automation <\/strong>ayuda a reducir errores humanos y garantiza resultados m\u00e1s fiables. Bien utilizados, estos entornos fortalecen la resiliencia empresarial al proteger datos cr\u00edticos y asegurar su integridad y disponibilidad.<\/p>\n\n\n\n

Program aims <\/h3>\n\n\n\n
    \n
  • Dise\u00f1ar una arquitectura Disaster Recovery<\/strong> activa-pasiva entre Azure y GPC que sea escalable y resistente a fallos.<\/li>\n\n\n\n
  • Lograr un Tiempo de Recuperaci\u00f3n o RTO de 30 minutos<\/strong> para la infraestructura y los recursos cr\u00edticos del negocio.<\/li>\n\n\n\n
  • Conseguir que el Punto de Recuperaci\u00f3n o RPO sea de 30 minutos<\/strong> para la base de datos del negocio.<\/li>\n\n\n\n
  • Dise\u00f1ar una estrategia de despliegue y gesti\u00f3n automatizada<\/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

      El proyecto consigui\u00f3 automatizar la transferencia peri\u00f3dica de backups de Azure a GCP, superando varios desaf\u00edos y reduciendo costes al centralizar el almacenamiento en un \u00fanico bucket.<\/p>\n\n\n\n

      Los beneficios que aporta el proyecto a una organizaci\u00f3n son:<\/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

        Este proyecto demostr\u00f3 una alternativa distinta a las soluciones habituales de los proveedores cloud para implementar un sistema de recuperaci\u00f3n ante desastres que garantice la continuidad del negocio y la protecci\u00f3n de datos cr\u00edticos. <\/p>\n\n\n\n

        Gracias al uso de Terraform, Azure DevOps y Kubernetes, se automatiz\u00f3 la Infraestructura como C\u00f3digo, facilitando la implementaci\u00f3n y gesti\u00f3n, mientras que la seguridad de las bases de datos se reforz\u00f3 mediante la automatizaci\u00f3n de backups con pipelines, asegurando su protecci\u00f3n y recuperaci\u00f3n en caso de desastre.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

        La automatizaci\u00f3n es crucial dentro del entorno cloud, ya que juega un papel clave en la obtenci\u00f3n de resultados consistentes y fiables. Adoptar esta pr\u00e1ctica permite estandarizar procesos y recursos limitados, adoptando buenas pr\u00e1cticas para mejorar la eficiencia operativa.<\/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"],"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}]}}