Celery NextGen: High Level Architecture #27
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
auvipy
reviewed
Jun 1, 2020
auvipy
reviewed
Jun 1, 2020
thedrow
force-pushed
the
high-level-architecture
branch
from
4091bee
to
b1cd5ce
Compare
|
This is ready for the first round of reviews. |
sorry somehow missed the notification |
auvipy
reviewed
Dec 18, 2020
|
|
||
| Abstract | ||
| ======== | ||
| Celery 5 is the next major version of Celery, and so we can break backward compatibility, even in significant ways. |
There was a problem hiding this comment.
maybe we could change this to a gradual incremental architectural overhaul?
| Other runtimes will be considered in different CEPs on a case-by-case basis. | ||
|
|
||
| As a general guideline, we will attempt to keep support for the latest Python version :term:`PyPy` supports. | ||
| However, if the need arises we will opt to use new Python language features and hope :term:`PyPy` can catch up. |
| Celery now allows connecting to multiple :term:`Message Brokers <Message Broker>` | ||
| even if they are of clusters that use different implementations of a message broker. | ||
|
|
||
| Users can consume messages from a Redis cluster, a RabbitMQ cluster, and an ActiveMQ cluster if they so desire. |
| We extend the :term:`Result Backend` concept further to allow new use cases such: | ||
|
|
||
| - :term:`ETL`. | ||
| - :term:`Data Integration`. |
There was a problem hiding this comment.
isn't apache airflow doing this right?
| execution of tasks to ensure we maximize the utilization of all our resources | ||
| and to prevent expected errors. | ||
|
|
||
| That is why the Controller is now responsible for auto-scaling Celery instances, rate-limiting tasks, |
There was a problem hiding this comment.
any prototype or dummy API for that or example?
|
|
||
| The platform itself can be anything Celery can run on e.g.: Pre-fork, SystemD, OpenRC, Docker, Swarm, Kubernetes, Nomad. | ||
|
|
||
| Each implementation of the Platform Manager will be provided in a different package. |
There was a problem hiding this comment.
any hints on which celery team might rely on officially?
4 tasks
auvipy
approved these changes
Jan 4, 2021
|
we need another round of improvement IMHO as celery 6 is the next gen |
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.
Fixes #19.
You can find the preview here.