SOA understanding

What can I do with a service-oriented architecture?

What can I do with a service-oriented architecture?
The need for SOA stems from the need to make business IT systems more flexible to adapt to changes in the business. By allowing strongly defined relationships and specific implementations that are still flexible, IT systems can take advantage of the capabilities of existing systems, and they can be prepared to make some changes in the future to meet the interaction needs between them.

Here is a specific example. An apparel toy organization owns 1000 international chain stores, and they often need to change their designs to catch up with generation and technology trends. This may mean not only changing package and graphics, but even changing the experience  of learn and entertain. If the system between the retailer and the manufacturer is incompatible, then the replacement from one supplier to another may be a very complicated software process. By leveraging the operational flexibility of the WSDL interface, each company can keep their existing systems as they are, and just match the WSDL interface and formulate new service-level agreements, so that they do not have to completely refactor their software systems. This is a change in the level of business, that is, they change partners, and all business operations remain basically unchanged. Here, the business interface can be changed a little, but the internal operation does not need to be changed. The reason for this is only to be able to work with external partners.
The other form is internal change. In this change, the retail organization decides that it will also rent out some places in the chain retail store to small shops specializing in popular clothes. This can be seen as a store-in. -store) business model. Here, although most of the company’s business operations remain unchanged, they require new internal software to handle such rental arrangements. Although internal software systems can withstand comprehensive overhauls, they need to do so while not having a major impact on the interaction with existing supplier systems. In this case, the SOA model remains intact, but the internal implementation has changed. Although new aspects can be added to the SOA model to incorporate the responsibilities of the new rental arrangement, the normal retail management system continues as usual.
In order to continue the concept of internal change, IT managers may find that the new configuration of the software can also be used in another way, such as renting a place to paste posters for advertising. Here, new business proposals are made by reusing flexible SOA models in new designs. This is a new achievement from the SOA model, and it is also a new opportunity, and such new opportunities may not have been in the past.
Vertical changes are also possible, in which retailers change from selling their own clothing to renting out exclusively through store-in-store models. If the vertical change starts completely from the bottom, it will bring about a significant change in the structure of the SOA model, along with which there may be new systems, software, processes, and relationships. In this case, the benefit of the SOA model is that it considers issues from the perspective of business operations and processes rather than from the perspective of applications and procedures, which allows business management to clearly determine what needs to be added or modified based on business operations. Or delete. The software system can then be constructed in a way that is suitable for business processing, rather than other ways that are often seen on many existing software platforms.
As you can see, here, change and the SOA system’s ability to adapt to change are the most important parts. For developers, such changes are possible whether they are within or outside their scope of work, depending on whether there is a change that requires knowing how the interfaces are defined and how they are related to each other Interact. Unlike developers, the role of the architect is to cause major changes to the SOA model. This division of labor is to allow developers to focus on creating functional units defined as services, and architects and modelers to focus on how to properly organize these units. It has a history of more than ten years. Commonly used Unified Modeling Language (UML), and described as a model-driven architecture (Model-Driven Architecture, MDA).