Achieve development agility, improve run-time application resiliency, and deliver highly-responsive applications by adopting cloud-native design patterns and building cloud-aware applications. Forklifting applications into the cloud is relatively fast, but the simple path into the cloud does not create better software. End-users may still complain about your development velocity, operations may still struggle to maintain uptime guarantees, and development iterations may continue at a glacial pace. By iteratively applying cloud-native design patterns and re-architecting applications, teams reduce technical debt, deploy with confidence, and build highly scalable solutions. Cloud-aware applications embrace microservices, actor model interactions, map-reduce processing, shared-nothing architecture, and the thirteen dwarf patterns. Learn about cloud-native design practices and frameworks that help you optimize scalability, foster anti-fragility, and decompose application monoliths into cloud-native microservices. Chris describes how Kubernetes, Akka, Hadoop, Eureka, Hysterix, and other open source projects make cloud-native design and implementation an approachable proposition.

1. Chris Haddad
Chief Architect
haddadc@karux.net
@cobiacomm
EIGHT MILES HIGH:
BUILD CLOUD-NATIVE AND
CLOUD-AWARE SYSTEMS

2. • Why evolve?
• Cloud-Native Design Patterns
• Cloud-Native Frameworks

3. Status Quo?
• Development Velocity
• Development Iterations
• Reliability and Uptime
• Scale and Performance

4. Don’t Forklift Static Topologies into
the Cloud
Source: http://www.ibm.com/developerworks/websphere/techjournal/1001_vanrun/1001_vanrun.html

5. Free DevOps from
expensive static
deployments and
glacial refresh cycles

6. Deploy with Confidence
GOAL STATE
• Reduce Technical Debt
• Optimize Scalability
• Foster Anti-fragility and Resiliency
• Deliver Highly Responsive Applications

7. ANTI-FRAGILE CONTINUOUS
INTEGRATION/DELIVERY PATTERN
… to exert a constant stress on your
delivery and deployment process to
reduce its fragility so that releasing
becomes a boring, low-risk activity.
Jez Humble, “On Antifragility in Systems
and Organizational Structure”
http://continuousdelivery.com/2013/01/on-
antifragility-in-systems-and-
organizational-architecture/

8. Rapid, iterative, seamless, rolling updates.

10. Microservices, containerized, DevOps
CLOUD-NATIVE
Learn more at https://cncf.io/

11. Into Cloud-Native Microservices
DECOMPOSE MONOLITHS
• Bounded Context
• Small domain
• Run in it’s own process
• Service interface
• *owns data storage

12. IDENTIFY BOUNDED CONTEXTS AND
DOMAINS
Source: http://www.slideshare.net/aca_it/modularity-ddd

13. API-FIRST , SERVICE ORIENTED
Source: https://www.nginx.com/blog/introduction-to-microservices/

14. Spin up
discrete infrastructure services on demand.
Server Profile
• Lightweight
• Self-contained
• Deterministic
• Dynamic Discovery
• Dynamic Composition

15. Requires a next generation stack
MICROSERVICES
• Service Discovery
• Service Monitoring
• Circuit Breakers
• Full-Stack Templates

16. Server-side
SERVICE DISCOVERY
Source: https://www.nginx.com/blog/introduction-to-microservices/

17. Client-Side
SERVICE DISCOVERY
Source: https://www.nginx.com/blog/introduction-to-microservices/

18. SINGLE DEPENDENCY DELAY CAUSING
BLOCKING OF USER REQUEST
Source: http://www.slideshare.net/yang75108/antifragile-microservices-and-devops-a-study

19. ALL USER REQUESTS WILL BE BLOCKED AT
PEAK HOUR(CASCADING FAILURE)
Source: http://www.slideshare.net/yang75108/antifragile-microservices-and-devops-a-study

20. Fail-fast and dynamically reset
CIRCUIT BREAKER
Source: http://martinfowler.com/bliki/CircuitBreaker.html

21. CIRCUIT BREAKER & BULKHEAD
ISOLATION PATTERN
https://github.com/Netflix/Hystrix

22. • Service-Oriented
• Just a single service
• Compose multiple services
• Ask for run-time information
• Location
• Policies
• Respect Data Gravity
• Shard data
• Cache and Eventual consistency
Cloud-Aware Applications

23. • Actor-model interactions
• Map-reduce processing
• Event Sourcing
• Ephemeral Containers
Cloud-Native Design Patterns

24. Actor-model Interactions
CONCURRENT PROCESSING
Source: http://arild.github.io/akka-workshop/#7

25. Map-Reduce
DIVIDE AND CONQUER

26. Event Sourcing
SHARD AND SEPARATE
Source: http://martinfowler.com/eaaDev/EventSourcing.html

27. Ephemeral Containers
AGILE CONTINUOUS DELIVERY

28. NEW STACK REQUIREMENTS
• Self-contained, Lightweight, Minimalistic
• Service-Oriented, API-Friendly
• Powerful transport module
• Configuration Management
• Bootstrapping , dependency and Lifecycle
Management
• Runtime Insights and Diagnostics
• Service discovery
Spring Boot
http://projects.spring.io/spring-boot/
DropWizard
https://dropwizard.github.io/dropwizard/index.html
NetFlix Karyon
https://github.com/Netflix/karyon

29. • Software Defined Networking
• Weave
• Calico
• Flannel
•Container Scheduling and Orchestration
• Mesos
• Kubernetes
•Full Stack Templates
• Docker compose, Kubernetes
•Monitoring and Management
• Netflix Cloud OSS
•Service Discovery
• Eureka, Consul, etcd
CLOUD-NATIVE FRAMEWORKS

30. •Actor-Model
• Akka
•Map-Reduce
• Hadoop
• Kubernetes
•Eventual Consistency
• Cassandra
• Redis
•Circuit Breakers
• Hysterix
CLOUD-NATIVE FRAMEWORKS

31. Contact us at
http://karux.net
haddadc@karux.net
@cobiacomm
JOURNEY TO THE CLOUDS
• Re-shape Architecture
• Re-fresh Platform
• Re-build Team Collaboration
• Re-invent Delivery