How do enterprises choose the public cloud architecture?

There are many patterns or categories in the world of cloud computing that meet the architectural needs of the enterprise. Some of them can solve particular problems, such as SaaS (Security as a service) or Taas (test-as-service), and some can provide a complete platform, such as PAAs (platform or service) or Iaas (architecture as a service). They are all trade-offs, and each can only be used to solve different problems. But you have to weigh it against your own architecture. Therefore, the categories of services include storage, databases, information, processes, applications, platforms, consolidations, security, management, testing, and architecture.

You can further break it down into finer grained scenarios, or do not consider a service provider that can solve specific problems alone. As a result, fine-grained services include storage, database, thin, process, integration, security, management, and testing. Coarse-grained services include applications, platforms, and architectures.

This decomposition is useful because coarse-grained cloud computing providers can indeed be composed of fine-grained resources. For example, a separate PAAs (platform and service) provider can provide storage, database, process, security, and testing services.

However, while it can provide many fine-grained resources and thus make it easier for us to use cloud computing solutions, the actual requirements of the architecture remain the primary factor for decision makers to consider. You may find that choosing a few fine-grained cloud computing solutions is better suited to the architecture choices when considering your own needs, or considering how to effectively match the architecture. Therefore, it is necessary to base on the components of the architecture, consider other candidate cloud computing vendor Categories:

For processes, services consist of applications, platforms, architectures, processes, and consolidations.

For data, services are applied, platform, architecture, storage, database, and information.

For services, services consist of applications, platforms, architectures, and information.

Process: Implement process services through Appian.

Data: Implement architecture services through Amazon's EC2, and implement database services via Amazon's simple db.

Services: Implement architecture services through Amazon's EC2.

You can keep the data in the Amazon's simple db or Amazon's EC2 platform. You can then create or host services on the Amazon EC2 platform with a custom application server provided by the platform. Finally, you might want to use the Appian platform because the process is on that platform. Remember, processes are connected to services, services are connected to data. You just have to choose the target platform.

In the choice of cloud computing service providers, we can give you some more specific examples:

Process: Through the Appian implementation process services, through the saleforce.com implementation of application services.

Data: Implement architecture services via 3Tera Cloudware and Amazon EC2, and implement database services through Amazon Simple DB.

Services: Implement architecture services via Amazon EC2 and 3Tera Cloudware, implement application services through Salesforce.com, and implement platform services through Saleforce.com force.com.

Or you just need to use a separate cloud vendor:

Process/Data/services: Implementing Process services via Amazon EC2.

In addition, you need to consider the other core elements of the architecture that can be customized for deployment in the cloud, including security, testing, and management, depending on your actual requirements. The goal of this walkthrough is to clarify the number of optional schemas you have and how you can integrate these choices into the final architecture, which requires a trade-off based on the actual situation.

There is also a high-level process that can be used to find the right type of cloud computing and the right to help you move processes, services, and data cloud providers.

The core steps are as follows:

1. List candidate platforms.

2. Analyze and test candidate platforms.

3. Select the target platform.

4. Deploy the data to the target platform.

(Responsible editor: The good of the Legacy)