Reasons for facing the design and construction of an own cloud architecture

We are still going through the fascination era of cloud computing services, which offer advantages in terms of prices, scalability, and data management. 

arquitectura cloud, proteccion privada y almacenamiento en la nube

Among other things, these services provide the possibility of focusing on the business itself and enhancing the customer experience, leaving the IT infrastructure in good hands and with reasonable costs, not to mention the clear benefits of lower cost cloud storage.

However, doubts also begin to appear due to some important disadvantages presented by this model, basically linked to the possibility of being hostage of the big players in the market (AWS, Azure, Google, IBM, etc). That is why we must highlight the desirability of designing a company’s own cloud architecture, regardless of the large supplies of cloud technology solutions.

Defining you own cloud architecture

Let’s briefly review the benefits of designing a corporate cloud architecture within a company:

√ Independence: Designing and constructing a corporate cloud architecture, allows the possibility to migrate a supplier’s application in the cloud to another infrastructure without major setbacks vs relying on the cloud provider to handle this.

 

√    Protection of the vendor from lock-in: Having your own cloud architecture means you’re not left in a situation where it’s not possible (or very difficult) to switch to alternative suppliers. The idea is to have a cloud design, software development blueprint, and corporate architecture independent of the infrastructure and technology solutions offer by the different cloud providers. 

 

   Adaptability: Having your own cloud architecture facilitates a much easier adaptation to the geographical distribution of the suppliers (for example, if they open a datacenter in a more accessible or nearby place), improving the latency times in the experience of the end users, and in the integration with other system and platforms either on or off premise. 

 

   Lower costs: By having more independence from a given cloud vendor that comes from owning your own architecture, you have more negotiating power when it comes to cloud vendor pricing and allows you to adapt your own infrastructure faster if the cloud vendor in question changes pricing for a sub-set of services. 

 

√ Multi-cloud: Having a cloud architecture separate from any one single vendor means you can deploy a distributed application solution across different suppliers. This concept is known as multi-cloud architecture design, and allows you to implement components in different cloud suppliers, and even in a company’s own data center on premise. 

 

  Resilience: You can substantially improve the resilience level of your applications and diversifying the risk especially in the case of a recovery disaster resulting from a failure coming from one of the cloud suppliers. If you maintain a replication scheme, or an agnostic cloud architecture design, it’s going to be easier to redeploy the application on the servers of another cloud provider and continue in contingency mode until the primary vendor becomes operational again. 

 

Not a private cloud

Keep in mind, in this article we are not talking about designing a private cloud – despite it’s greatest advantages around areas such as data protection. This is instead referring to having a cloud architecture that allows you to have more control over your cloud deployment, regardless of the cloud supplie

Along with designing a multi-cloud architecture that’s vendor independent, software development must respect certain rules so as not to tie the technical solution to a static design, along with constructing a scalable solution. Finally, the architecture must have development and deployment pipelines as automated as possible.

You can be sure that thinking, designing, and building your own cloud architecture based on an abstraction level that allows applications to be as independent as possible from a specific cloud supplier, will help you avoid getting stuck to one vendor in particular. In order to do this, it’s necessary to at least design an architecture that contemplates un-coupling from specific cloud services – building for instance a layer that is a wrapper between the application and the services that are available. In this video, for example, you can see how Mercado Libre made it’s own architecture called Fury; https://www.linkedin.com/posts/joelvera_gracias-mercadolibre-aws-ugcPost-6567042386701107200-wwCr/

Have you had any experience designing a cloud architecture that is independent of vendors? We invite you to share below! 

Contact Us

info@baufest.com


© 2018 Baufest. All rights reserved. Privacy Policy.