HashiConf 2024 Now streaming live from Boston! Attend for free

Use case

Multi-platform service mesh with Consul

Use Consul service mesh to securely connect applications on any runtime, any cloud, or on-premises environments.

Challenge

Services across multiple clouds

Multi-cloud is a core strategy and a natural progression as customers migrate to the public cloud. Customers are moving many applications to the cloud while keeping others on-premises. Customers are also adopting microservices, many of which need to communicate with existing legacy services. This is a common scenario where customers now struggle to manage and connect their services in a consistent manner across different clouds, platforms, runtimes, and networks.

Solution

Consistency across multiple clouds and platforms

Deploy in any public cloud or on-premises environment and on any deployment type, including VMs, Kubernetes, or Nomad. This consistent dataplane allows developers to connect their services between heterogeneous environments regardless of whether they are running on VMs in an on-premises datacenter or on a managed Kubernetes service like EKS, AKS, or GKE.

Consul supports true multi-tenancy with administrative partitions. Multiple deployments can remain under a single control plane, allowing for consistent management and governance while maintaining autonomy and isolation for different tenants. Operators can choose to self-manage their own Consul deployments or opt for a fully managed solution with HCP for Consul.

Consul service mesh can deploy in any environment and supports multiple runtimes, including Kubernetes, Nomad, and VMs.
Hear how Tide abandoned its adoption of AWS AppMesh in favor of HashiCorp Consul, making the transition in only 6 weeks with no downtime and no big-bang migration.
Hear how Tide abandoned its adoption of AWS AppMesh in favor of HashiCorp Consul, making the transition in only 6 weeks with no downtime and no big-bang migration.
Customer case study

Tide's self-service service mesh with HCP Consul

​​Learn how Tide abandoned its adoption of AWS AppMesh in favor of HashiCorp Consul, making the transition in only 6 weeks with no downtime and no big-bang migration.

Read more

Tutorials

Explore all

Docs

Explore all