Cleaning up directory
This commit is contained in:
23
equinix/api-team/proposals/scalable-api.org
Normal file
23
equinix/api-team/proposals/scalable-api.org
Normal file
@@ -0,0 +1,23 @@
|
||||
#+TITLE: Scalable API
|
||||
#+AUTHOR: Adam Mohammed
|
||||
|
||||
* Overview
|
||||
|
||||
In this document we take a look at the concept of breaking the
|
||||
monolith from the start. By that I mean, what do we hope to achieve
|
||||
with the breaking the monolith. From there we can identify the
|
||||
problems we're trying to solve.
|
||||
|
||||
Part of the problem (I have) with the "breaking the monolith" phrase is the
|
||||
vision is too lofty. That phrase isn't a vision it's snake-oil. The
|
||||
promised land we hope to get to is a place where teams are able to
|
||||
focus on delivering business value and new features to customers that
|
||||
are meaningful, leverage our existing differentiators, and enable new
|
||||
differentiators.
|
||||
|
||||
What do we believe is preventing us from delivering business value quickly
|
||||
currently? What we identify there is a hypothesis and based on some
|
||||
level of intuition, so it's a great start for an attempt to optimize
|
||||
the process. It's even better if we can quantify how much effort is
|
||||
spent doing these speed-inhibiting activities, so we know we're
|
||||
optimizing our bottlenecks.
|
||||
Reference in New Issue
Block a user