Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update image and address comments

Browse Source
This commit is contained in:
krish7919 (Krish) 2017-09-26 12:16:34 +02:00 committed by Krish
parent 1761e94840
commit cebea3e1b8
3 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/server/source/_static/arch.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 52 KiB

2
docs/server/source/_static/arch.svg
View File

File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 30 KiB

11
docs/server/source/production-deployment-template/architecture.rst
View File

@ -8,20 +8,20 @@ An IPDB Production deployment is hosted on a Kubernetes cluster and includes:
* NGINX, OpenResty, BigchainDB, Monitoring Agent and Backup Agent * NGINX, OpenResty, BigchainDB, Monitoring Agent and Backup Agent
`Kubernetes Deployments <https://kubernetes.io/docs/concepts/workloads/controllers/deployment/>`_. `Kubernetes Deployments <https://kubernetes.io/docs/concepts/workloads/controllers/deployment/>`_.
* MongoDB `Kubernetes StatefulSet <https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/>`_. * MongoDB `Kubernetes StatefulSet <https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/>`_.
* External systems like `3scale <https://3scale.net>`_, * Third party systems like `3scale <https://3scale.net>`_,
`MongoDB Cloud Manager <https://cloud.mongodb.com>`_ and the `MongoDB Cloud Manager <https://cloud.mongodb.com>`_ and the
`Azure Operations Management Suite `Azure Operations Management Suite
<https://docs.microsoft.com/en-us/azure/operations-management-suite/>`_. <https://docs.microsoft.com/en-us/azure/operations-management-suite/>`_.
.. image:: ../_static/arch.svg .. image:: ../_static/arch.jpg
We describe the role of each of these modules here.
NGINX NGINX
----- -----
We use an NGINX as HTTP proxy on port 443 at the cloud entrypoint for: We use an NGINX as HTTP proxy on port 443 (configurable) at the cloud
entrypoint for:
#. Rate Limiting: We configure NGINX to allow only a certain number of requests #. Rate Limiting: We configure NGINX to allow only a certain number of requests
(configurable) which prevents DoS attacks. (configurable) which prevents DoS attacks.
@ -36,7 +36,8 @@ We use an NGINX as HTTP proxy on port 443 at the cloud entrypoint for:
#. BigchainDB Service if it is a GET request. #. BigchainDB Service if it is a GET request.
We use an NGINX TCP proxy on port 27017 at the cloud entrypoint for: We use an NGINX TCP proxy on port 27017 (configurable) at the cloud
entrypoint for:
#. Rate Limiting: We configure NGINX to allow only a certain number of requests #. Rate Limiting: We configure NGINX to allow only a certain number of requests
(configurable) which prevents DoS attacks. (configurable) which prevents DoS attacks.