rework the "CDS Origins" documentation section #2632
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
rayene
commented
May 3, 2018
rayene
commented
- Description: Major rework the "CDS Origins" documentation section. I've removed a lot of text to keep the focus on the important design principles.
- Related issues: No related issues.
- About tests: I've run the hugo server locally and reviewed the result before creating the PR
- Mentions: @ovh/cds
|
Note: Some pics may need to be removed from the repo [after discussing with the team]. |
sguiheux
requested changes
May 4, 2018
|
|
||
| « 100,000 jobs are launched every week » | ||
| CDS's API servers are completely stateless. They do not store anything on the fileSystem. Whith this "share-nothing" architecture, servers can be deployed as much times as reauired to support the load. Instances can be spawned and decommissioned dynamically to handle usage surges when required while keeping the cost at its lowest when the platform is underused. All you need to provide is a scalable and highly available database. |
There was a problem hiding this comment.
Whith => with
reauired => required
| - There is no instance "master": we can update any instance CDS at any time. | ||
| - No data is stored on the FileSystem of the CDS API. User data is stored in a PostgreSQL database. | ||
| - To limit frequent SQL queries on the database, some data is stored in a Redis. | ||
| An ingenious system of variables allows to customize the build runs depending on the apps to be built and on the deployment environments. |
There was a problem hiding this comment.
An ingenious system of variables / . A system of templating ?
|
|
||
| ### 5 - Reuse Pipelines | ||
| CDS can be fully operated through its RESTful API. The API is used by the CDS's UI but also by the workers. All components speak the same language: REST. |
yesnault
approved these changes
May 9, 2018
sguiheux
approved these changes
May 9, 2018
bnjjj
approved these changes
May 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.