Choose four of the primary design principles of SOA and explain how they differ from the goals of traditional software development.

Service
loose coupling is the idea that the service is only loosely connected with dependent
applications or users. This maintains a level of separation and distinction to ensure that the
service is unchangeable and can't be restricted to the use of one subset of users. Most other
software is developed specifically for a client, or uses a database strictly defined by the
client. Service loose coupling ensures that the service is repeatable and reusable for multiple
clients.

Service abstraction is the obfuscation of the design architecture so
that the system seems seamless and impenetrable to the client. Most modern software is somewhat
visible to clients, especially if it was a software suite purchased with full adaptability by
the client so that they can tweak it.

Service autonomy is the function of
designing a service that does not rely on any other services or applications to run. This makes
a very robust system that is harder to hack or crash. This is difficult, since it is easier to
develop dependent systemsand so most software platforms are not autonomous.

Service discoverability is another design function. It is the ease and availability of
the program in a traditional search. Essentially, it means the service and its functions are in
plain text English, which is less common since most code is written with computer standards in
place, instead of regular linguistics.