The document discusses modern application delivery challenges and how HashiCorp's Consul service mesh can address these issues by facilitating service discovery, traffic security, and efficient routing across various platforms, including legacy applications and Kubernetes. It emphasizes that Consul is versatile and can support multiple operating systems and cloud environments, making it suitable for a wide range of applications. Additionally, it presents features like dynamic service configuration and advanced routing capabilities, showcasing a demo of traffic routing and securing between services.

1. Modern Application
Delivery with Consul

2. Talk Agenda
● Who am I?
● Who is Hashicorp?
● Challenges with modern application delivery
● How Consul’s service mesh features can help
● But service mesh is just for containers, right?
● Demo

3. Who Am I?
Ehron Gwinn
Staff Solutions Engineer at
Hashicorp

4. Hashicorp Company Overview
Founded in 2012 by Mitchell Hashimoto and
Armon Dadgar
Enabling the Cloud Operating Model Provision,
Secure, Connect, and Run any infrastructure for
any application

5. Copyright © 2019 HashiCorp ⁄
The Transition to Multi-Cloud
Copyright © 2019 HashiCorp ⁄ 5
Traditional
Datacenter
“Static”
Dedicated
Infrastructure
Modern
Datacenter
“Dynamic”
AWS Azure GCP+ + +Private Cloud +

6. Copyright © 2018 HashiCorp ⁄Copyright © 2018 HashiCorp ⁄ 6
App
App
Networking
Development
Security
Operations
A Common Cloud Operating Model
to Accelerate Application Delivery
POLICY
GOVERNANCE

7. © 2018 HashiCorpCONSUL ADOPTION
50k+
457 Contributors
Used at scale with 50k+ agents
Consul is
mature
and
battle hardened!
1M+
12K+
2014
Monthly downloads
GitHub Stars
Product Launch
7

8. Solve Challenges
with distributed
applications
Enter the service mesh!
▪ Service discovery
▪ Securing traffic between VMs/services
▪ Efficient traffic routing and automatic
failover (even across
datacenters/clouds!)
▪ Dynamic service configuration (canary
deploys, feature flags, etc)
▪ L7 routing, tracing, circuit breaking,
observability, and more
Why do you need a service
mesh?

9. Cool story, bro.
But service
mesh is just for
containers,
right?

10. No! Consul runs virtually everywhere!
● Consul is available for nearly
every OS found in the
datacenter
● Consul can be used in both
legacy (or as I like to call them,
revenue generating) apps, and
bleeding edge platforms
including Kubernetes,
Functions AAS, etc.
● In fact, Consul provides a
bridge from legacy apps to the
cloud, containers, and beyond

11. Crawl -> Walk -> Run
Steps to modernize existing infrastructure,
and building blocks for the future

12. 1 2 3
DNS Service
Discovery
● Build and maintain a service catalog
of healthy, available services.
● Dynamically drive load balancer
config both on-prem and in the cloud,
or bypass LBs altogether where
appropriate
● Dramatically decrease TTV with
automation

13. 1 2 3
TLS Everywhere
● Use Consul Connect to simplify
network security between services
in both local and remote
datacenters and clouds
● Define “intentions” that define
authorization policies between
services
● Easily and securely connect legacy
on-prem apps with Kubernetes
and other new platforms

14. 1 2 3
Advanced
Functionality
● Progressive delivery with
features such as canary testing,
blue-green deploys, A/B
testing, feature toggling, etc
● Deploy Consul across the org
to bring these capabilities to
on-prem and cloud, legacy and
beyond!

15. Demo!
Routing and securing
traffic between services
with Consul
● Multi-DC/cloud
● Automatic Failover
● TLS Everywhere!!
● NO VPNS!

16. Example App
● Three tier (or really small
microservices) app
● Services run on separate
instances (VMs)
● Communicate via network
calls
● https://github.com/norhe/m
ultidc_connect

17. Example App
● Both network
encryption and failover
is handled
transparently by Consul
● Simplify app dev by
handling encryption,
retries, circuit breaking,
etc, at the infra layer

18. www.hashicorp.com
ehron@hashicorp.com
Thank you!