Is it advisable to use containerised Azurite for production like environment?
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 393
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
### Which service(blob, file, queue, table) does this issue concern?
Blob and Table Storage
### Which version of the Azurite was used?
V3
### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
DockerHub
### What problem was encountered?
Scalability and Concurrency Limitations
We are working on a project where one of our clients requires their files (blob and table storage) to be held on their on-prem-datacentre. We were considering Containerised Azurite as a potential candidate for this requirement. Having worked with Azurite in the past for local development and testing, we were wondering if it is advisable to take it a step further into Production.
So far, we understand that Azurite has scaling and concurrency limitations - but will configuring data and metadata persistency to a production like server help mitigate these limitations?
We would be grateful for any feedback.
Regards,
Arun Pillai
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.