An imprecise term referring to a means for integrating a mesh of collaborating services on a platform-independent basis through middleware that treats each disparate application as a service.
(1) (Start Of Authority) The first record in a DNS zone file. See DNS records.
(2) (Service-Oriented Architecture) The modularization of business functions for greater flexibility and reusability. Instead of building monolithic applications for each department, an SOA organizes business software in a granular fashion so that common functions can be used interchangeably by different departments internally and by external business partners as well. The more granular the components (the more pieces), the more they can be reused. SOA is a way of thinking about IT assets as service components. When functions in a large application are made into stand-alone services that can be accessed separately, they are beneficial to several parties. Standard Interfaces An SOA is implemented via a programming interface (API) that allows components to communicate with each other. The most popular interface is the use of XML over HTTP, known as "Web services." However, SOAs are also implemented via the .NET Framework and Java EE/RMI, as well as CORBA and DCOM, the latter two being the earliest SOA interfaces, then known as "distributed object systems." CICS, IBM's MQ series and other message passing protocols could also be considered SOA interfaces. See Web services.