Ken Sipe

To 99.99 and Beyond

Tuesday, 7:00 PM EST

When architecting a critical system the Availability 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.

After establishing high availability expectations and measurements, this session will dive into what it takes to establish the highest scale possible. It includes a look at infrastructure needs with a separation between capacity and scale. A look a service discovery with pro and cons of service to service dependencies. We look at infrastructure necessary such as health checks and monitoring. The session will include a look at different layers of fault domains including cross region.

Micro-Service Fundamentals

Wednesday, 3:00 PM EST

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.

This session will touch on the topics of:

• 12-factor application development
• Cloud / datacenter Infrastructure
• Application Categorizations
  • Guaranteed vs Best of Service
  • Core business vs supportive services
  • SLA
    • Response time require
    • Availability require
    • Fastlane / slowlane
    • App affinity / anti-affinity
• Service Discovery and Service Elasticity
• Fault domain
• Multi-tenant
• Metrics
• Tracing
• Debugging
• Capacity vs Scale

Real-world examples will provide working and non-working examples throughout. If you are looking to mature your applications into a set of micro-service this is the session for you.

Micro-Service Orchestration Deep Dive

Wednesday, 5:00 PM EST

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.

Presented by an engineer that has worked for over 6 years with Docker and container orchestrators. Attendees will leave with a clear understanding of the Kubernetes API, scheduler, controllers and operators, and how they are different than the Mesos 2-level scheduler. The session will include how resources are managed in the cluster along with pod life-cycle management. The session will call out topics of concern regarding availability and scalability and how to best manage those concerns.

Architectural Awareness: Engineering Super-skill

Wednesday, 7:00 PM EST

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.

Within this session we look holistically an engineering, architecture and the software development process. Discussing:

* Awareness of when process needs to change (original purpose of Agile)
* Awareness of architectural complexity
* Awareness of a shift in architectural needs 
* Awareness of application portfolio and application categorization 
* Awareness of metrics surfacing system challenges
* Awareness of system scale (and what scale means for your application)
* Awareness when architectural rules are changing
* Awareness of motivation for feature requests
* Awareness of solving the right problem

The focus of the session will be mindful (defined as focusing on one's awareness), commentating in sharing strategies for heightening awareness as an architect and engineer.