KenSipe

Awareness is the knowledge or perception of a situation or fact, which based on myriad of factors is an elusive attribute. Likely the most significant unasked for skill... perhaps because it's challenging to "measure" or verify. It is challenging to be aware of aware, or is evidence of it's adherence. This session will cover different levels of architectural awareness. How to surface awareness and how you might respond to different technical situations once you are aware.

As you look towards micro-service based solutions, or maturing your existing, there are a number of factors that are fundamental worth being aware of. This sessions covers the gambit of architectural topics you need to understand to be successful.

Leading technical organizations in micro-service based architectures all use an orchestrator in their datacenter; be it Apache Mesos, Kubernetes, Tupperware, the Borg or Omega. The dominate platforms in the open source space are Kubernetes and Mesos. This session will dive deep into the core difference including: * Pod container lifecycle differences * In production scaling differences * Scheduling and orchestration management difference * Reconciliation management * Resource selection (affinity vs anti-affinity) * Service discovery This is NOT a one is better than the other smack-down. There are pro/con consequences for each orchestrator.

When architecting a critical system the *A*vailability of CAP theorem becomes the most important element. Architecture measures availability in 9s with 99.99% equating less than 1 hour of unplanned downtime. This session will focus on what it takes to get there.