copy code,drag or close
Anyone who has not been submersed in the entire development life-cycle of a large scale e-commerce solution could be forgiven for not realising that the Web sites front end E-commerce system represents less than half of the development effort in constructing a complete real world E-commerce system.
Leaving aside the great marketing some software companies do ot use their products, coupled with our eagerness to implement E-commerce solutions developers and managers somtimes need to be reminded about some of the facts.
They are that existing retailers and wholesalers already have pre-existing backend systems such as accounting, stock control and shipping and that any new serious, public facing front end system must tie into the existing process, and that can mean the front end site "talking" each of the existing systems.
Shipping in this case does not refer to shipping the goods to the Web site customer; it refers to movement of materials and supplies involved with the production or manufacture of the goods the enterprise sells, so resource shipping
Service Oriented Architecture is an unbrella term for new designs that meet the need for existing systems to “talk-to-each-other”, to be able to exchange data, information and records to keep the whole business running is underlying driving force.
There are many perspectives and definitions surrounding these needs, the most useful way of understanding all of these complexities is to describe them as the messaging that needs to take place within the supply chain.
In practice SOA is implemented with industry standard protocols such as XML, it’s important to note that these protocols do change, after all XML is extensible and that means it will change as a result of revision.
Whilst all systems should be designed to be low maintenance, there is some benefit here in thinking about the publication delivery and consumption of any particular service.
When designing an ERP system using SOA there are a number of key principals to bear in mind; the delivery will change and must be able to change as technologies change.
It is details of the architecture that will change, the design principals will not change.
This means the publication and consumption of any service which will continue to use the same architecture, the same design principle and as such can be considered as unchanging.