|Uke||Start dato Start||Sluttdato||Frist||Sted||Språk|
|12||20.03.2017 20.03.17||21.03.2017||20.03.2017||Glasspaper AS, Sandbrogaten 5, 5003 Bergen, Bergen, Hordaland||Glasspaper AS, Sandbrogaten 5, 5003 Bergen, Bergen||Norsk|
|12||22.03.2017 22.03.17||23.03.2017||22.03.2017||Glasspaper AS, Strandveien 43, 7042 Trondheim, Trondheim, Sør-Trøndelag||Glasspaper AS, Strandveien 43, 7042 Trondheim, Trondheim||Norsk|
|16||20.04.2017 20.04.17||21.04.2017||20.04.2017||Glasspaper AS, Brynsveien 12, 0667 Oslo, Oslo||Glasspaper AS, Brynsveien 12, 0667 Oslo, Oslo||Norsk|
|26||29.06.2017 29.06.17||30.06.2017||29.06.2017||Glasspaper AS, Brynsveien 12, 0667 Oslo, Oslo||Glasspaper AS, Brynsveien 12, 0667 Oslo, Oslo||Norsk|
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.
Key Architectural Principles
Key Technological Principles
Key Information Principles
Approaches to SOA
Designing Services around Operations
Operational Implementation: Web Services
Evaluation of the Operational Approach
Designing with Commands and Events
Messaging Implementation Example
Evaluation of the messaging approach
Introduction to REST
REST meets Messaging
Evaluating the RESTful approach
Governance and agility
SOA and Testing
SOA and Security
Summing Up SOA
Glasspaper as sine hjemmesider
The course assumes a general awareness of software development, but does not require recent programming experience nor experience as an architect. However, having played either of these roles will help you to get more out of the course. Taking our Software Architecture course first is not required, but will leave you better prepared for this one.
Project leaders, architects and system developers who want to gain an understanding - or improve their basic understanding - of SOA.
Del gjerne din erfaring eller tanker om dette kurset eller temaet med andre!