Du har valgt: SOA - Service oriented architecture


Oslo 2 dager 14 900 kr
16 Feb
06 Apr
06 Apr
What does Service Oriented Architecture really mean? When is it relevant? Why might it be interesting? What are the risks? [+]
What does Service Oriented Architecture really mean? When is it relevant? Why might it be interesting? What are the risks? How does it relate to technologies such as web services, message queues and service busses? How does it fit in with business processes, modeling and agility? And - most critically - how can it be put to use in order to build solutions that deliver value, enable the business to evolve, and are reliable, scalable and secure? This course tackles all of these questions head on. Using an example business throughout the course, issues relating to the design, modeling, publication and ongoing governance of services are examined. And - while this is not a course requiring programming knowledge from attendees - multiple sample implementations of the system will be used to illustrate and explore the impact of various design and technology choices. Drawing on pertinent underlying theory, while remaining relentlessly practical, this course examines the choices and challenges facing those who approach SOA today.   Course Outline DAY 1 Key Architectural Principles What is an architecture, anyway? Business Processes Domain Models and Bounded Contexts The need for agility and deferred decision making Service Level Agreement Key Technological Principles Distributed systems: a short history Consequences of distribution Synchronous vs. asynchornous Cohesion, coupling and autonomy Endpoints Key Information Principles The Information Silo problem Information ownership and authority The command/event distinction Transactions The CAP theorem and eventual consistency Approaches to SOA The operational approach The messaging approach The RESTful approach Introduction to the sample business used in the course Designing Services around Operations Modeling processes into services Service classification Designing contracts Operational Implementation: Web Services No, Web Services != SOA Why deliver services over the web? XML SOAP WSDL Exploring a sample implementation Considering asynchrony and polling Evaluation of the Operational Approach Consequences for modeling Latency Reliability When things get loopy Messaging Preliminaries Commands and events revisited Publish subscribe Message queues, store and forward Messages busses Brokers vs. busses Designing with Commands and Events Identifying commands and events from the process Workflows and sagas What is the contract here? What is the service here? Messaging Implementation Example Exploring the implementation Examining the event flows How reliability is improved Sagas Evaluation of the messaging approach Consequences for modeling Latency and consistency Reliability DAY 2 Introduction to REST HTTP revisited Resources How resources relate to the domain Hypermedia As The Engine Of Application State Designing RESTfully Processes, behaviors and hypermedia Resources What is the contract with a RESTful system? RESTful Implementation Exploring the sample implementation Correct usage of HTTP status codes Approaches to hypermedia Media types and content negotiation REST meets Messaging Events and feeds Atom, or something else? Polling: not so stupid after all To bus or not to bus? Evaluating the RESTful approach Consequences for modeling Latency and consistency Reliability Governance and agility What is governance? The service portfolio Publishing services and contracts Evolving services and contracts Contract versioning considerations Monitoring and quality of service SOA and Testing Why test? Testing at the service level Testing service integration Chaos monkey SOA and Security Cofidentiality and encryption Integrity and digital signatures Authentication and authorization Summing Up SOA Contrasting approaches with regard to modeling Contrasting approaches with regard to coupling and autonomy Contrasting approaches with regard to reliability SOA opportunities SOA risks Key things to remember   Modern Service Oriented Architecture Glasspaper as sine hjemmesider [-]
Les mer

Lukk Denne siden benytter seg av informasjonskapsler (cookies).
Du kan fortsette å bruke siden som vanlig hvis du godtar dette. Les mer om bruk av informasjonskapsler i vår personvernerklæring.