SOA Patterns

Services Should be: loosely coupled, course grained, stateless, idempotent, reusable and composable. Service Virtualization is a pattern that shield service consumers from changes in service providers.
Canonical Data Model should be used to reduce the number of data transformations needed when interacting with more than two systems.
Compensations vs. Transactions.
Content based routing and filtering: ESB
Best practices in a SOA project
Service Registry is a central part of the SOA governance. Services should be organized and documented. (services should be visible and discoverable|
Service Categorization and Namig Convention should be established to enable transparency. Services and Processes – the commons and the differences. Risk assesment
Cross Specialization Teams should be established to leverage the experiences and skill for the various integrated systems.
SOA Antipatterns
I will mention a few anit-patterns and bad practices. The list will be provided later.

Detalji o predavanju

Vrsta: Predavanje / Lecture

Razina težine: Srednje detaljno / Detailed

Poželjno iskustvo slušatelja: Bez iskustva (1 g. i manje) / No experinace

Poželjna funkcija slušatelja:
Krajnji korisnik / End User
Sistem Analitičar / System Analist
Developer
Dizajner / Designer
Menadžer - operativni / Manager - Operational

Predviđeno vrijeme trajanja rada - aktivnosti: 45 min

904_Ryman SOA-Patterns.pdf 625,33 kB

O predavaču