-
-
Notifications
You must be signed in to change notification settings - Fork 749
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
Azure Blob Storage as storage backend for Persisted Operations #7777
base: main
Are you sure you want to change the base?
Conversation
Hey @cimnine thanks for your contribution. Tell us when you need a review. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7777 +/- ##
=======================================
Coverage 74.32% 74.33%
=======================================
Files 2860 2864 +4
Lines 149842 149914 +72
Branches 17411 17421 +10
=======================================
+ Hits 111373 111439 +66
- Misses 32671 32674 +3
- Partials 5798 5801 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
16298f8
to
686a709
Compare
@michaelstaib I believe now it would be ready for a first round of scrutiny. |
686a709
to
6e8df7e
Compare
@michaelstaib what are the next steps here? |
I will have a look today |
This PR proposes a new adapter to use Azure Blob Storage as storage backend for (automatically) persisted operations.
At least on Azure, Redis-compatible cache instances are comparably costly and mounting a shared filesystem is not always possible – and often not desired either. The Blob Storage on the other end is almost free.
Also, it's relatively easy to upload persisted operations extracted from a client in a CI/CD pipeline, whereas this is tricky with the existing options.
Please let me know if you're interested in including this as an officially supported storage backend. Otherwise, I will probably publish it independently.