Service orientation

Question 1

IT problems in large organizations:

Answer 1

• Software systems are not flexible (changes are slow and expensive)
• Information silos (inconsistent data definitions, duplication of software processes, no integration and no reuse)
• Lack of overview

Question 2

information silos =

Answer 2

isolated or segregated collections of data within an organization that are not easily accessible or shared with other parts of the organization.

Question 3

Enterprise architecture =

Answer 3

defines basic standards, structures, transportation pathways.

Question 4

orchestration =

Answer 4

allows the combination of service executions in a specific sequence to satisfy a business process.

Question 5

orchestration, functionalities/charachteristics:

Answer 5

o Orchestration services usually require that a special processing engine be plugged into the ESB specifically to orchestrate services
o Orchestration is typically scripted using BPEL (Business Process Language)
o Orchestration allows the creation of services using other services as building blocks increasing reuse and allowing IT to more flexibly adapt to business changes

Question 6

Enterprise Service Bus (ESB) = (-> backbone of SOA)

Answer 6

a standards-based integration platform combining messaging, web services, data transformation and dynamic routing.

Question 7

Governance =

Answer 7

organizing principles and rules that determine how an organization should behave

Question 8

SOA inhibitors (= factors or challenges that hinder the adoption, implementation, or success of SOA initiatives within an organization):

Answer 8

• Impact on existing applications (monolithic and home-grown not designed for linking)
• Business and IT governance (giving up the silos)
• Change in software development (from coding to modeling)
• Performance (additional overhead incurred by invoking a service via en ESB, not directly)

Question 9

Gartner hype cycle

Question 10

Microservices … etc.