status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

remove before/after diagram

This commit is contained in:
nicolelyn 2020-05-01 13:14:20 -04:00 committed by Brandon Romano
parent 1887f1cb40
commit 3e47ad5aed
2 changed files with 0 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
website/pages/discovery/index.jsx
View File

@ -1,7 +1,6 @@
import CallToAction from '@hashicorp/react-call-to-action'
import CaseStudySlider from '@hashicorp/react-case-study-slider'
import CodeBlock from '@hashicorp/react-code-block'
import BeforeAfterDiagram from '../../components/before-after'
export default function ServiceDiscovery() {
return (
@ -20,24 +19,6 @@ export default function ServiceDiscovery() {
},
]}
/>
<section
id="static-dynamic"
className="g-section-block layout-vertical theme-white-background-black-text small-padding"
>
<div className="g-grid-container">
<BeforeAfterDiagram
beforeHeading="The Challenge"
beforeSubTitle="Service load balancers aren't efficient in a dynamic world."
beforeImage="/img/consul-connect/svgs/discovery-challenge.svg"
beforeDescription="Load balancers are often used to front a service tier and provide a static IP. These load balancers add cost, increase latency, introduce single points of failure, and must be updated as services scale up/down."
afterHeading="The Solution"
afterSubTitle="Service discovery for dynamic infrastructure."
afterImage="/img/consul-connect/svgs/discovery-solution.svg"
afterDescription="Instead of load balancers, connectivity in dynamic infrastructure is best solved with service discovery. Service discovery uses a registry to keep a real-time list of services, their location, and their health. Services query the registry to discover the location of upstream services and then connect directly. This allows services to scale up/down and gracefully handle failure without a load balancer intermediary."
/>
</div>
</section>
<section></section>
<section class="g-section border-top large-padding">
<div class="g-container">

18
website/pages/mesh/index.jsx
View File

@ -1,6 +1,5 @@
import CallToAction from '@hashicorp/react-call-to-action'
import CodeBlock from '@hashicorp/react-code-block'
import BeforeAfterDiagram from '../../components/before-after'
export default function ServiceMesh() {
return (
@ -19,23 +18,6 @@ export default function ServiceMesh() {
},
]}
/>
<section
id="static-dynamic"
className="g-section-block layout-vertical theme-white-background-black-text small-padding"
>
<div className="g-grid-container">
<BeforeAfterDiagram
beforeHeading="The Challenge"
beforeSubTitle="Network appliances, like load balancers or firewalls with manual processes, don't scale in dynamic settings to support modern applications."
beforeImage="/img/consul-connect/svgs/segmentation-challenge.svg"
beforeDescription="East-west firewalls use IP-based rules to secure ingress and egress traffic. But in a dynamic world where services move across machines and machines are frequently created and destroyed, this perimeter-based approach is difficult to scale as it results in complex network topologies and a sprawl of short-lived firewall rules and proxy configuration."
afterHeading="The Solution"
afterSubTitle="Service mesh as an automated and distributed approach to networking and security that can operate across platforms and private and public cloud"
afterImage="/img/consul-connect/svgs/segmentation-solution.svg"
afterDescription="Service mesh is a new approach to secure the service itself rather than relying on the network. Consul uses centrally managed service policies and configuration to enable dynamic routing and security based on service identity. These policies scale across datacenters and large fleets without IP-based rules or networking middleware."
/>
</div>
</section>
<section class="g-section border-top large-padding">
<div class="g-container">