Service orientation: change ideas from five aspects

Does the enterprise confirm that the enterprise architecture is really ready for cloud computing? Or cloud computing is really suitable for enterprise architecture? The advent of cloud computing has indeed led to the development of some different ways of thinking, but in fact these "new" ideas are not that new.

Chris Bruzzi and Nick Hamm from Appirio, a provider of IT and cloud computing consulting services, have published an article where two of them shared with CIOs some personal experience with cloud application development. They pointed out in the article that in the process of application development and deployment, performers should pay attention to changing their own habits in five ways in order to better implement cloud computing for the enterprise. Now, these ideas still apply.

For the architects and developers who have experience working in the SOA (Service Oriented Architecture) area, most of the most successful practice stories are very similar. However, Bruzzi and Hamm consider the SOA architecture of the past to be very limited because it is always blocked by the overall enterprise architecture. However, as more and more enterprise IT is turning to cloud computing, people really should rethink the "service-oriented" thinking:

1. The use of modular approach to the design of architectural solutions: first consider clearly what the needs of the enterprise, and then design a solution composed of multiple loosely coupled components to meet the overall needs of the enterprise. This will indeed increase the workload of the previous period, but in the latter period, the rewards will be much greater than the rewards.

2. Exceed the application development language to examine the API interface: 10 years ago, the so-called IT business is not a Java store or a .NET store. Cloud computing has led the issue from the application to the application development language and service delivery platform. This means that cloud computing architects also need to turn their attention from technical or developmental languages ​​to architectural services and APIs that use these technologies and languages.

3. Reuse components as much as possible: The components in these cloud computing initiatives may already be working effectively, whether they come from cloud computing vendors inside or outside the enterprise's own library, such as Salesfroce. com and Amazon Web Services (Amazon Web Services), can be reused.

4. Expand the team as outsource: Watch out for the developer community, such as CloudSpokes or 99Designs, and look for new components there. The benefit of doing so is that applications can be built faster and without being limited by the overall technical capabilities of your team. Many creative solutions are designed in this situation.

5. Evaluate internal applications: In cloud computing solutions, there is a wealth of data available on the configuration, coding, quality, etc. of internal applications for evaluation. Some cloud computing solution providers also collect these benchmark values, but they certainly do not provide all the information they need, so architects need to do their own collection.