4 ms·

Sure, 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 f

Sure, 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 ago
I 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 ago
  Was 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 ago
    Yes, 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 ago
  I 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 ago
    At the time the client wanted to stay inside of the Azure ecosystem so Atlas and the like weren't seriously considered.
habeebtc 5y ago
As 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.

Bellyache5 5y ago

I 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 ago
Was 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 ago
  Yes, 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 ago
I 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 ago
  At the time the client wanted to stay inside of the Azure ecosystem so Atlas and the like weren't seriously considered.

habeebtc 5y ago

As 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.