Erik Drolshammer Stig Lau Whydah r u t

Agenda 1. Hva er IAM, Whydah 2. Arkitekturgjennomgang

• Admin GUI • Admin API • High Availability & High Scalability Features

“Clear and consistent responsibility power all great architectures”

Single Sign-On made easy Session control The vault of users and applications Administration GUI

Guts on the Outside Inner architecture ” the implementation architecture of the microservices themselves”

Characteristics of a Microservice Architecture 1. 2. 3. 4. 5. 6. 7. 8. 9.

© 2005, 2006, 2007 by Bjørn Erik Pedersen

Robustness principle, aka. Postel’s law: "Be conservative in what you send, be liberal in

X Evolving Service Endpoint Consumer-Driven Contracts Hypermedia as the Engine of Application State (HATEOAS)

Spring MVC Spring Io. C Jetty Jersey Guice Grizzly Javascript Python Java Jersey Guice

. . . skal Stig snakke mer om etterpå 1. 2. 3. 4. Enterprise

Tjenester vil feile! • Tjenester må kunne startes i vilkårlig rekkefølge • Retry-mekanismer hvis

Infrastruktur • HTTPS overalt, alltid! • Web proxy • Lastbalanserer • Discovery • Hazelcast

db domain web http: //www. javapractices. com/topic/Topic. Action. do? Id=205, http: //www. web 4

Erik Drolshammer erik@fjas. no @Sherriff 1

Slides: 31

Download presentation

Erik Drolshammer Stig Lau

Whydah r u t k e t i k r A r e g n i r a f r e

Agenda 1. Hva er IAM, Whydah 2. Arkitekturgjennomgang

• Admin GUI • Admin API • High Availability & High Scalability Features • User authentication & authorization • Single Sign-On • Application authentication & authorization

CC BY-NC-SA 2. 0

“Clear and consistent responsibility power all great architectures”

Single Sign-On made easy Session control The vault of users and applications Administration GUI Administration APIs

Guts on the Outside Inner architecture ” the implementation architecture of the microservices themselves” Outer architecture ”the platform capabilities you need to help all those simple little microservices (and their Dev. Ops teams) work together to make good on the promises of flexible and scalable development and deployment. ” Gary Olliffe, http: //blogs. gartner. com/gary-olliffe/2015/01/30/microservices-guts-on-the-outside/

Characteristics of a Microservice Architecture 1. 2. 3. 4. 5. 6. 7. 8. 9. Componentization via Services (Team) Organized around Business Capabilities Products not Projects Smart endpoints and dumb pipes Decentralized Governance Decentralized Data Management Infrastructure Automation Design for failure Evolutionary Design http: //martinfowler. com/articles/microservices. html James Lewis Martin Fowler

S t r a m s e p i p

Robustness principle, aka. Postel’s law: "Be conservative in what you send, be liberal in what you accept"

X Evolving Service Endpoint Consumer-Driven Contracts Hypermedia as the Engine of Application State (HATEOAS)

Spring MVC Spring Io. C Jetty Jersey Guice Grizzly Javascript Python Java Jersey Guice Grizzly Angular Spring MVC Spring Io. C Jetty Jersey Spring Io. C Jetty

Polyglot persistence

. . . skal Stig snakke mer om etterpå 1. 2. 3. 4. Enterprise Maven Infrastructure Provisjonering: Ansible + Amazon EC 2 Automated deployment (wget, upstart, java –jar) Automatic (automated + cron)

Tjenester vil feile! • Tjenester må kunne startes i vilkårlig rekkefølge • Retry-mekanismer hvis en tjeneste er utilgjengelig. • Håndtere feilsituasjoner • Robuste start/stopp-script • Saklig logging under oppstart • Logge inngående og utgående kall • Bruk log levels aktivt

Infrastruktur • HTTPS overalt, alltid! • Web proxy • Lastbalanserer • Discovery • Hazelcast for HA Elastic Load Balancing