Skip to main content

For any additional questions you have about this concept, check out our FAQ page.



Because all of the cloud service providers have their own limitations and challenges, there is an architectural gap when enterprises start using the cloud. This is because there is no reference architecture to help guide enterprises as they transition into the cloud, causing issues with the networking itself and security.



This is where Aviatrix comes in with the Multi-Cloud Network Architecture. It provides a cloud agnostic framework that can easily be replicated.



 



The Components of the MCNA





  1. The Cloud Core has the applications connecting to the Global Transit Layer, which is a unified, global data plane across multiple/single clouds.


  2. The Cloud Access Layer is where the on-prem components connect to the cloud.


  3. The Cloud Security should be embedded in the Cloud Core Layer and the Cloud Access layer, because the public cloud is a shared infrastructure. This can be seen in the MCN Architecture when the Cloud Security layer cuts through the others.


  4. Similarly, the Cloud Operations layer makes Day 1, 2, and 3 operations accessible to all the parts of the cloud. This allows troubleshooting and visibility.




The Benefits of the MCNA Approach





  • The architecture is easily replicated in the Aviatrix controller.


  • There is a normalized data plane.


  • Service insertion and chaining are easily configured through the transit layer.




For more information, watch the video above.

Multi-cloud strategy is the concomitant use of two or more cloud services such as AWS, Azure, Google Cloud and more.



This means you can use Google cloud to serve your US users and Microsoft Azure for your customers in Europe.



Or you might use Azure SQL for your databases and Cognito for user management while using AWS EC2 instances and Load Balancing, all for a single application.



In addition, you can run your app primarily on Digital Ocean but is completely replicated and backed up on AWS.



You can run different app on different clouds. You can have your development and test environments on one cloud, and your production environment on another.



Multi-cloud management is another aspect, which involves monitoring cost of cloud deployment . It is important to reap benefits of multi-cloud.



Here is an add on to the post 



Multi-cloud strategy is particularly effective if enterprises dealing with below challenges:





  • Users are not located near any data center, or widely distributed geographically.


  • Facing regulations limit in particular countries for storing data, e.g., EU.


  • Environment where public clouds are used with on-premises resources.


  • Cloud-based application is not resilient which can affect disaster recovery when loss of a single data center.




Multi-Cloud Architecture



In order to build highly scalable and reliable applications, a multi-cloud architecture design is appropriate. Our objective is to provide architectural guidance for migrating cloud-based systems that run on multiple independent clouds. Let’s take a look at some of the prominent multi-cloud architectures and migration strategy.



Cloudification



In this architecture, application component is hosted on-premise and after migration, it can use different cloud services of other cloud platforms to improve performance.



Here application component C1 is been hosted on-premise but after adopting multi-cloud, it uses AWS storage service AWS S3 and for compute, it uses Azure virtual machines.



Benefits: Improves availability as application re-hosting in multiple cloud platforms and avoid vendor lock-in.



Multi-Cloud Relocation



In this architecture application component is re-hosted on cloud platform and use other cloud services of multiple cloud platform to enhance capabilities 



Here application component C1 is re-hosted on AWS platform after migration and open to use environmental services of Azure. It is using AWS S3 for storage and has option available for compute either AWS or Azure.



Benefits: Improves availability as application re-hosting in multiple cloud platforms and avoid vendor lock-in.



Multi-Cloud Refactor



To provide better QoS, an on-premise application is re-architected for deployment on multiple cloud platforms. Here application needs to re-architected as fine-grained components so that deployment of high-usage components can be optimized independently. Here deployment of high-usage components is optimized independently of low-usage ones. The parallel design enables better throughput to multi-cloud platforms.



Here AC1 and AC2 are two application components hosted on-premise before migration. As both the components are independent integrity units, AC1 is deployed on AWS using AWS S3. On the other hand, AC2 is deployed on Azure and it can use any Azure’s cloud service as per requirements.



Benefits: Optimal scalability/performance, range of multi-cloud deployment options, agility to respond to business/IT change.



Challenges: On-premise application is modernized in isolation. Modernization is performed primarily for technical reasons. Component architecture which is only determined bottom-up may need to be re-evaluated because of multi-cloud environment.



Multi-Cloud Rebinding



A re-architected application is deployed partially on multiple cloud environments and enables the application to continue to function using secondary deployment when there is a failure with the primary platform.



Multi-Cloud Rebinding with Cloud Brokerage



A re-architected application is deployed partially on multiple cloud environments. This enables the application to continue to function using secondary deployment when there is a failure with the primary platform using cloud brokerage services.



Multi-Application Modernization



Different on-premise applications A1/A2, AC1 are re-architected as a portfolio and deployed on cloud environment.



I hope This Post is helpful and has given add on

whats wrong with the modules have watched the video 4 times but cant proceed.

Joshua Obiabo Ehoche also completed my test with 10/10

Reply


Terms & Conditions