معماری سرویس گرا

تحلیل یک پروژه آزمایشی

Now to start SOA You are ready, you need to choose a test project. But do not know how to do this project Select.
Use the following criteria for a project to be considered a pilot project:
1- Does this project meet business values?
2- Does this project have a limited field of activity?
3- Does this project make a good service?
4- Do the team members have a correct understanding of the issues that the project refers to?
5- Is the project useful but not for critical missions?
Paying attention to the mentioned criteria will help you to choose the right project to start.

Service Oriented Architecture/ SOA

Does this project meet business values?
SOA aligns IT with the business in many ways, which is why there are blurred lines between the two. has it. How SOA emerges is highly dependent on your organization and its culture. However, SOA needs support It is significant. It offers new ways of thinking about systems and many APIs to learn There is. With free and open-source tools for using servers, gateways to critical services, implementing acquisition processes And more work, some companies buy expensive software that takes a lot of time and input from the business are in need The investment that the business makes to train the team and expand the IT group means real cost and time. That In the beginning, nothing new is given to take. Often this investment is seen as an underlying cost for infrastructure It comes as the business expects to pay in the long run.
For these reasons, the business win is important or the investment associated with the SOA team may be lost. The way to business success The job is to provide money. Choose a project that has a quick return on investment that will support the business. It is abundantly clear that the true return on investment from SOA will be realized after several years, and depends on responsiveness and readiness IT needs to meet the changing needs of the business.
Does a project have a limited scope?
It is better for a project to have a limited field of activity and an application that is relative to systems that are not known show clearly This means that it is better for your project to include multiple systems. This issue cannot be merely a reason The concept is a web service, but it must be a complete and real project.
Introducing SOA can expose software developers to new APIs, new server software, new languages, and so on. Direct new constructions. It also provides a new way of thinking about software development. For services think with Thinking for things is different. Changing direction from functional and procedural programming to object-oriented programming takes time and involves changes It is significant for software developers. For example, Java language classes amounting to 15,000 program lines with a single method They have 700, 800 lines. Just because you have written a program in Java language and the program is not object oriented and cannot be expected It was working well. The difference that services can make for object-oriented programmers should not be underestimated took You need time to train the team (although not at the same time.) which takes away the time of the programmers Takes. If the project has a wide field of activity, when you pay attention to the side issues, it is possible to never go to do not end
You want to be able to isolate the unknowns so that you can easily solve the problem during the development and quality assurance phase Identify the project. Pay attention to choose a product that uses new products. The team must be able to Ability to work with new infrastructures and APIs. A counselor can also help here.
Pay attention to the customers' goals in the first service. By responding to internal issues in the business, your risk is relative to Reduce customer contact. This gives you time before the outside world gets involved and new and impossible topics Introduce forecasting, build some infrastructure. Naturally, the services used will help you to run the services Focus your new self well and keep you away from difficult and complex topics like unified security for a while. also Internal services give you the opportunity to measure traffic volume more reliably.
Does the project make a good service?
Be careful not to force external forces to choose a test project even if the proposed project does not make a good service. The SOA team is formed, and then the project manager insists that everything in the listed project must be experimental, just Whether this candidate service is useful or not. Writing services at the beginning incurs a lot of complexity and cost to the project he does. Hoping that the gains are more valuable later. If the service is never used again or from the base If the other one is not summoned, you do not have the right service. This means you didn't realize much ROI.
Do the team members have a correct understanding of the issues that the project refers to?
If you have a discussion topic specific to the problem area at hand, you can reduce the risk significantly give Bringing up new systems, new software, new processes and new issues at the same time as services and SOA introduces creates a dangerous combination. If you work with vendors or consultants, make sure they are a They have a mental background of what you defined at the top of your business.
Is the project useful but not for critical missions?
While understanding the business value of implementing SOA is important, be careful not to lose too much in the first step. Project SOA trials often fail to track completion, miss clear requirements, or fail altogether. is faced Choose a project that does not analyze your business for additional work in order to grow and implement services.
This makes the weak points in the service a pilot project. A little bit on architecture format, methodology, and Research the plan template and choose the one that supports you in a better environment.

Pilot Project Analysis

The second project
When you reach the end of the first project, the second project, which is probably considered a trial, becomes very important. The main objective Creating the foundation of SOA is understanding the technical concepts, creating something of value using new constraints and new strategies.
The second project provides a key opportunity to build some of the enterprise interfaces and horizontal slicing made easy by SOA. To For this reason, the second project also requires the limitation of the business area like the first project. No need to write infrastructures Not new for the second project. You need time to learn new behavior patterns, your new tools and reality training You are running the production services environment daily to get started.
You can also build your own primary architecture using the second project. you can Guide services practical and functional Add rules services and security services to your project. At this point you may Introduce BAM tools or generally work with WS-policy or more security interfaces. You may Clarify how you deal with service versioning that is not the focus of the pilot project. Maybe some One of the good features of orchestration is that it will be beneficial to you, rather than the fact that you may not have the time and need to explore have primary
These things need to be sorted out in the SOA path. The path of SOA changes but it must be kept up to date, and remember that SOA It is a long-term investment. Think big but act smart.