Skip to content
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

Add CosmosDB storage backend #5185

Merged
merged 3 commits into from
Nov 21, 2018
Merged

Add CosmosDB storage backend #5185

merged 3 commits into from
Nov 21, 2018

Conversation

c-w
Copy link
Contributor

@c-w c-w commented Nov 20, 2018

Description

This change adds a new results backend. The backend is implemented on top of the pydocumentdb library which uses Azure CosmosDB for a scalable, globally replicated, high-performance, low-latency and high-throughput PaaS backend.

The backend can be activated by setting the results backend URL to cosmosdbsql://:{PrimaryKey}@{AccountName}.documents.azure.com where the PrimaryKey and AccountName can be found in the Azure Portal, on the keys pane of your CosmosDB resource (see screenshot below highlighting the PrimaryKey in orange and AccountName in purple).

Screenshot of Azure Portal with CosmosDB PrimaryKey (orange) and AccountName (purple)

This pull request is a follow-up from #4720 so tagging @georgepsarakis for review.

This change adds a new results backend. The backend is implemented on
top of the pydocumentdb library [1] which uses Azure CosmosDB [2] for a
scalable, globally replicated, high-performance, low-latency and
high-throughput PaaS backend.

[1] https://github.com/Azure/azure-documentdb-python

[2] https://azure.microsoft.com/en-us/services/cosmos-db/
Copy link
Member

@thedrow thedrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@thedrow thedrow merged commit 4d90741 into celery:master Nov 21, 2018
@c-w c-w deleted the cosmosdb-backend branch November 21, 2018 14:46
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants