-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rework the "CDS Origins" documentation section #2632
Conversation
rayene
commented
May 3, 2018
- 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]. |
|
||
« 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RESTFul => REST
Signed-off-by: Yvonnick Esnault <[email protected]>
Signed-off-by: Yvonnick Esnault <[email protected]>