Explain the service oriented architecture (SOA) and its characteristics.

 Service-oriented architecture (SOA)

 Service-oriented architecture (SOA) references a set of principles and methodologies applied by software engineers to design and develop software in the form of interoperable services. Services are usually built in the form of components that can be reused for different purposes than originally intended. For this reason, the interfaces are often defined in a practical manner, allowing use across varying applications and multiple platforms.

The principal characteristics of SOA are described in more detail here:

  • SOA is black-box component architecture. The black box lets you reuse existing business applications; it simply adds a fairly simple adapter to them. You don’t need to know every detail of what’s inside each component; SOA hides the complexity whenever possible.
  • SOA components are loosely coupled. Software components are loosely coupled if they’re designed to interact in a standardized way that minimizes dependencies. One loosely coupled component passes data to another component and makes a request; the second component carries out the request and, if necessary, passes data back to the first. Each component offers a small range of simple services to other components. A set of loosely coupled components does the same work that software components in tightly structured applications used to do, but with loose coupling, you can combine and recombine the components in a bunch of ways. This makes a world of difference in the ability to make changes easily, accurately, and quickly.
  • SOA components are orchestrated to link through business processes to deliver a well-defined level of service. SOA creates a simple arrangement of components that, together, deliver a very complex business service. Simultaneously, SOA must provide acceptable service levels. To that end, the components ensure a dependable service level. Service level is tied directly to the best practices of conducting business, commonly referred to as business process management (BPM).
  •  BPM focuses on the effective design of business processes and SOA allows IT to align with business processes.

Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

Discuss classification or taxonomy of virtualization at different levels.