The Cloud Platform Integration Framework (CPIF) provides an enterprise or cloud service provider architect patterns that helps bridge the gaps between infrastructure and workloads by providing guidance to application and workload teams for integrating with the Microsoft cloud platform.
Cloud Platform Integration Framework Overview and Patterns:
- Focus on enabling hybrid cloud solutions
- Provide a lightweight framework for cloud integration which is application across diverse workloads
- Surface practical examples of Azure design patterns
- Minimize the need for customer development
These patterns have been proven in the field are based on Microsoft Consulting Services field experience. There are a number of pattern guides available and each of the patterns guides includes:
- An overview that includes requirements and service description for the pattern
- Architecture patterns dependencies, considerations, and component Azure services
- Information on Interfaces and endpoints
- Coverage of availability and performance considerations
- A composite service level agreement (SLA)
- Cost considerations, including cost factors and cost drivers
- Operations considerations, such as CPIF deployment, monitoring, update and business continuity and disaster recovery (BC/DR)
- Architectural anti-patterns
The following Cloud Platform Integration Framework (CPIF) patterns are currently available:
This article discusses each of the pillars of the Cloud Platform Integration Framework and goes into details of how each of the pattern documents are structured
This article provides an overview of Microsoft Azure networking capabilities for hybrid environments. Microsoft Azure Virtual Networking enables you to create logically isolated networks in Azure and securely connect them to your on-premises datacenter over the Internet or using a private network connection.
This article provides details of Azure Search Tier design pattern which includes the Azure features and services required to deliver search services that can provide predictable performance and high availability across geographic boundaries and provides an architectural pattern for using Azure Search in delivering a search solution.
The Multi-Site Data Tier design pattern details the Azure features and services required to deliver data tier services that can provide predictable performance and high availability across geographic boundaries.
This article describes the Offsite Batch Processing Tier design pattern and details the Azure features and services required to deliver backend data processing that is both fault tolerant and scalable. These services are realized as worker roles in cloud services on Azure, which currently can be deployed to any Azure data center.
The Global Load Balanced Web Tier design pattern details the Azure features and services required to deliver web tier services that can provide predictable performance and high availability across geographic boundaries.
We hope that you’ll find these patterns helpful when you architect and design solutions that integrate your on-premises environments with the Microsoft Azure public cloud. More are coming in the future, so stay tuned to this space!
If you have questions or suggestions for integration patterns to be included in the future, please leave a comment at the bottom of this page. If you prefer, you can email me, Tom Shinder, at firstname.lastname@example.org I will make sure that the team gets your input and I’ll get you a response quickly.