4 ms·
Speaking of CosmosDB -- other than this security issue -- has anyone here ever used it for anything practical? To me it seemed vaguely interesting but a little
by jiggawatts 5y ago
Speaking of CosmosDB -- other than this security issue -- has anyone here ever used it for anything practical?
To me it seemed vaguely interesting but a little bit overpriced for real-world usage outside of fortune 500s or big government, where budgets aren't always a concern.
- thrixton 5y agoSure, as an entity store for run of the mill CRUD apps. It has a MongoDB API Layer and a Cassandra API Layer (as well as SQL which is preferred). Works just fine, apparently cost can blow out though with high usage, I haven't got there yet. Does have a free tier.
- Bellyache5 5y agoI tried Cosmos via the Mongo compatibility layer and performance was abysmal, even when cranking the provisioned performance way up. I ended up getting significantly better performance from a reasonably sized MongoDB container running on AKS.
- tiew9Vii 5y agoWas this taking a MongoDB database app and pointing to CosmosDB or was this developing a app around CosmosDB's partitioning etc but using the MongoDB API for read/write? The former, lift and shift scenario I can understand as you need to structure your data to work best with CosmosDB/DynamoDB etc. If it's the latter that is useful to know as I'm currently building a POC on Azure so I should watch out for it.
- Bellyache5 5y agoYes, so not the ideal use case. The compatibility Cosmos offered was nice and didn't present any issues, it's just the performance that suffered. This was all part of a benchmarking exercise to figure out how to scale an app with minimal changes so we expected some performance penalty, just not as steep as what we observed.
- gqewogpdqa 5y agoI think that makes sense. Using the technology as designed without the “compatibility” layer is likely a better option. Thanks for sharing as many I think wonder about these DocumentDB and CosmosDB MongoDB imitators. However, CosmosDB is a managed service, easier than setting up your own database. Did you exclude Atlas from your conclusion for some reason? Ie did AKS do things that Atlas could not?
- Bellyache5 5y agoAt the time the client wanted to stay inside of the Azure ecosystem so Atlas and the like weren't seriously considered.
- habeebtc 5y agoAs I understand it (I do not know that much about it), Cosmos is a multitool with features to fit many, many use cases. You must be diligent to develop your application to use it efficiently from both a cost and performance/latency perspective. Those that put in the work may not love it, but they are very successful at operating at scale. Massive, insane scale.
- gnabgib 5y agoIts graph DB (Gremlin compatible) is pretty great.
- vyrotek 5y agoWe use it to log audit data for all platform events and changes to data. It's one thing we found the schemaless nature to be valuable for. The automatic indexing has worked well for reports.
- tiew9Vii 5y agoThe CosmosDB serverless pricing model seems very good value for small to medium usage. CosmosDB is also unique in it has geospatial type/query support which DynamoDB etc don't. I believe the serverless pricing is fairly recent so not sure if you checked the pricing before it was released, also on the pricing page you need to specifically click the "Serverless" tab which isn't to obvious as a clickable tab in the UI. I've recently tested it as needed geospartial query support for a hobby project and the cost is cents per month with the serverless pricing model. I'm also accessing CosmosDB outside of Azure to use low cost VPS hosting and latency is pretty acceptable for web type stuff. If you are DB read/write heavy obviously pricing is going to be higher due to pay for what you use, pre-provisioned pricing will become the better value option at that point.
- w0m 5y agoThis. I couldn't justify it prior to the serverless introduction; but I'm doing 1m+ ops/mo now for <1usd for some high-concurrency state tracking ops.
- fatbird 5y agoI recently set it up as the ingestion point for an IOT pipeline that currently runs steadily at a high volume, and found that Cosmos would charge me $15k/month in RUs to achieve stable ingestion (i.e., no 429s on intermittent spikes). This was fed by Stream Analytics fed by an eventhub. For comparison, I had the same eventhub feed Kafka Connect to dump it into Mongo 5.0's new timestream collections on a $200/month VM, and after running both outputs at full volume for a couple days, Azure offered me a helpful suggestion to downsize the under-utilized VM and save money. I haven't quite figured out if the RU rate is just too high to be economical, and counts on large orgs with large data to expect a large bill; or if the RU model simple works badly for high velocity data. I've verified that the pricing model now scales down properly for small/medium loads, at which point the various high availability/geographcial distribution features really add value. I'm trying to conceptualize how the RU cost, amortized across longer term storage and less demanding ingress/egress schedules, can work out. For our scenario, Cosmos functionally offers exactly the horizontal scalability we need. As a different sanity check, I set up a SQL Server account as the ingestion database and saw comparable costs, so it wasn't that Cosmos itself has an unworkable pricing model.
- gautamdivgi 5y agoHave used the SQL and Gremlin(Graph) varieties. Heavy load on the SQL, not so much on the graph. Works well. The main advantage is extremely low "devops". There is also the added benefit of setting up a geo-redundant cluster while keeping the extremely low "devops" theme which I intend to explore. We use it with a private endpoint and turn off public access. I've been generally happy with it.
- UK-Al05 5y agoYes. A large 4 TB oltp database as a document store. As long you have a good partitioning strategy seems work without much effort put into it.