diff --git a/website/_redirects b/website/_redirects index 10a84a8d4..91d76cb71 100644 --- a/website/_redirects +++ b/website/_redirects @@ -5,6 +5,8 @@ # Consul Redirects +/discovery.html /use-cases/service-discovery-and-health-checking 301! +/mesh.html /use-cases/multi-platform-service-mesh 301! /api.html /api-docs 301! /docs/agent/acl-rules.html /docs/acl/acl-rules 301! /docs/agent/acl-rules /docs/acl/acl-rules 301! diff --git a/website/pages/discovery/index.jsx b/website/pages/discovery/index.jsx deleted file mode 100644 index 2547cdd92..000000000 --- a/website/pages/discovery/index.jsx +++ /dev/null @@ -1,480 +0,0 @@ -import CallToAction from '@hashicorp/react-call-to-action' -import CaseStudySlider from '@hashicorp/react-case-study-slider' -import CodeBlock from '@hashicorp/react-code-block' - -export default function ServiceDiscovery() { - return ( - <> -
- Consul provides a registry of all the running nodes and - services, along with their current health status. This - allows operators to understand the environment, and - applications and automation tools to interact with dynamic - infrastructure using an HTTP API. -
-- - Learn more - - -
-- Consul enables service discovery using a built-in DNS - server. This allows existing applications to easily - integrate, as almost all applications support using DNS to - resolve IP addresses. Using DNS instead of a static IP - address allows services to scale up/down and route around - failures easily. -
-- - Learn more - - -
-- Consul provides an HTTP API to query the service registry - for nodes, services, and health check information. The API - also supports blocking queries, or long-polling for any - changes. This allows automation tools to react to services - being registered or health status changes to change - configurations or traffic routing in real time. -
-- - Learn more - - -
-- Consul supports multiple datacenters out of the box with no - complicated configuration. Look up services in other - datacenters or keep the request local. Advanced features - like Prepared Queries enable automatic failover to other - datacenters. -
-- - Learn more - - -
-- Pairing service discovery with health checking prevents - routing requests to unhealthy hosts and enables services to - easily provide circuit breakers. -
-- - Learn more - - -
-- Service-to-service communication policy at Layer 7 can be - managed centrally, enabling advanced traffic management - patterns such as service failover, path-based routing, and - traffic shifting that can be applied across public and - private clouds, platforms, and networks. -
-- - Learn more - - -
-- Centrally managed service observability at Layer 7 including - detailed metrics on all service-to-service communication - such as connections, bytes transferred, retries, timeouts, - open circuits, and request rates, response codes. -
-- - Learn more - - -
-- Secure communication between legacy and modern workloads. - Sidecar proxies allow applications to be integrated without - code changes and Layer 4 support provides nearly universal - protocol compatibility. -
-- - Learn more - - -
-- TLS certificates are used to identify services and secure - communications. Certificates use the SPIFFE format for - interoperability with other platforms. Consul can be a - certificate authority to simplify deployment, or integrate - with external signing authorities like Vault. -
-- - Learn more - - -
-- All traffic between services is encrypted and authenticated - with mutual TLS. Using TLS provides a strong guarantee of - the identity of services communicating, and ensures all data - in transit is encrypted. -
-- - Learn more - - -
-- Connect between different cloud regions, VPCs and between - overlay and underlay networks without complex network - tunnels and NAT. Mesh Gateways solve routing at TLS layer - while preserving end-to-end encryption and limiting attack - surface area at the edge of each network. -
-- - Learn more - - -
-