8ae3332165
- moved and renamed files/folders based on new structure - updated docs navigation based on new structure - moved CLI to top nav (created commands.jsx and commands-navigation.js) - updated and added redirects - updating to be consistent with standalone categories - changing "overview" link in top nav to lead to where intro was moved (docs/intro) - adding redirects for intro content - deleting old intro folders - format all data/navigation files - deleting old commands folder - reverting changes to glossary page - adjust intro navigation for removal of 'vs' paths - add helm page redirect - fix more redirects - add a missing redirect - fix broken anchor links and formatting mistakes - deleted duplicate section, added redirect, changed link - removed duplicate glossary page
37 lines
1.9 KiB
Plaintext
37 lines
1.9 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Consul vs. Custom Solutions
|
|
sidebar_title: Custom Solutions
|
|
description: >-
|
|
As a codebase grows, a monolithic app often evolves into a Service Oriented
|
|
Architecture (SOA). A universal pain point for SOA is service discovery and
|
|
configuration. In many cases, this leads to organizations building home grown
|
|
solutions. It is an undisputed fact that distributed systems are hard;
|
|
building one is error-prone and time-consuming. Most systems cut corners by
|
|
introducing single points of failure such as a single Redis or RDBMS to
|
|
maintain cluster state. These solutions may work in the short term, but they
|
|
are rarely fault tolerant or scalable. Besides these limitations, they require
|
|
time and resources to build and maintain.
|
|
---
|
|
|
|
# Consul vs. Custom Solutions
|
|
|
|
As a codebase grows, a monolithic app often evolves into a Service Oriented
|
|
Architecture (SOA). A universal pain point for SOA is service discovery and
|
|
configuration. In many cases, this leads to organizations building home grown
|
|
solutions. It is an undisputed fact that distributed systems are hard; building
|
|
one is error-prone and time-consuming. Most systems cut corners by introducing
|
|
single points of failure such as a single Redis or RDBMS to maintain cluster
|
|
state. These solutions may work in the short term, but they are rarely fault
|
|
tolerant or scalable. Besides these limitations, they require time and resources
|
|
to build and maintain.
|
|
|
|
Consul provides the core set of features needed by an SOA out of the box. By
|
|
using Consul, organizations can leverage open source work to reduce the time
|
|
and effort spent re-inventing the wheel and can focus instead on their business
|
|
applications.
|
|
|
|
Consul is built on well-cited research and is designed with the constraints of
|
|
distributed systems in mind. At every step, Consul takes efforts to provide a
|
|
robust and scalable solution for organizations of any size.
|