The Secret to SOA is approaching the Primitive

Service-Oriented Architecture Diagram

Service-Oriented Architecture (SOA) is a type of software design where services are provided to the other components by application components

SOA works through a communication protocol over a network. The basic principles of service-oriented architecture are independent of vendors, products and technologies.

SOA is clearly rebounding, generally around the arising use of cloud computing. Why? We’ll when we’re dealing with clouds, we’re dealing with services, and when we’re dealing with services we ought to be dealing with SOA. Make good sense?

The common method to SOA is to specify sets of services that could exist physically within the data center, on a public cloud, or possibly in both locations (hybrid cloud). The degree that these services provide useful behavior, and functional habits expected to information, really goes to the value. Nevertheless, I would also state that we have to think about the quality of the services design, the granularity, or how well the services approach a “useful primitive,” and therefore providing even more value.

The capability to create, specify, and establish services at a primitive level goes to the value of those services thinking about that it’s a lot easier to create composites from teams of primitive services. Thus, allowing you to mix and match services to measure up to the specific purpose/requirements of the composite service, procedure, or application, instead of attempting to handle services that are to high level, or course grained, and therefore not a precise fit for your requirements.

An example that I would use is that it’s much simpler to construct a customized developed home using wood, fasteners, or other individual products than to build a home from pieces of another house. The even more primitive the parts, the more versatility you have when developing solutions. As opposed to attempting to recycle a living room.

This is of specific value when thinking about cloud computing. You desire to expose services that offer really primitive and low-level functions, and thus are better to those that want to consume them. Public clouds service providers get this, and therefore provide lots of primitive APIs that appear intricate, but provide a lot more value to those looking to develop company option.

It is necessary that you consider the levels that you specify services, and the more primitive the better. I understand that is a bit counter intuitive, however many aspects of great SOA are. When thinking SOA, inform everyone you’re taking the most primitive strategy.

service-oriented architecture