Micro Services Containers, Reactive Manifesto and… Identity

From IIW
Jump to: navigation, search

Session Topic: Microservices/Containers/Reactive Manifesto and Identity

Thursday 1F

Convener: Dave Sanford

Notes-taker: Dave Sanford

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:

Dave Sanford started essentially by playing buzzword bingo by creating a list of related topics related to the software/system architecture that apparently many big Internet players have been using for some time, however more details are becoming well known:

  • App containers
  • Loosely coupled
  • Message driven
  • Elastic scaling
  • Event driven
  • Hybrid/Multi-presence (buy the base, rent the spike)
  • Complex event processing
  • Minimize required state

Dave then gave the rap that this is becoming more predominant within the industry, but also as the containers become more lightweight, micro-services can become smaller and this merges with the kinds of personal instances that this community is very interested in (Personal cloud, IoT, PICOs, PDS, ...)

Hugh Pyle (Qredo) discussed thinking of everything as streams, back pressure and viewing event streams as being pulled from the end rather than pushed through. Hugh described 'reactive systems' as primarily composed of a finite set of simple and composable primitives (map, filter, join, reduce, partition, ..) that interact with these flows. By making many of these actions as 'idempotent' there is less worry about the costs of maintaining state.

Discussions included how hadoop is batch oriented vs. Twitter's storm as being real-time.

Phil Windley showed slides and described the PICO architecture of Fuse as microservices and some of the advantages of that architecture.

Hugh also showed some reactive Java (RXJava?) code and how it provided that pull flow characteristics.

Finally we started talking about how Fuse uses OAuth and how that is probably a good model for managing the identity of microservices and authorizations in this space.