Learn More
Resend Email
2
yamlbreakfast
355d

Using AWS DocumentDB elastic cluster for a sharded managed MongoDB
It's ass is so heavy!! More than 15min for scaling 2 -> 3 shards!
Am I taking a bad decision?

rant

mongodb

slow

documentdb

aws
Favorite
Ranter
Comments
  • 3
    355d
    Yes.
  • 0
    355d
    @NeatNerdPrime the answer I needed to hear. Thanks fellow human.
  • 1
    355d
    is it because the provisioning of the 3rd shard is slow? Or there is a huge amount of data to relocate?
  • 1
    355d
    @asgs yes, provisioning that 3rd shard (or Nth shard) takes a looot (+15mins)
    I'd understand it if it was a loaded cluster holding many GBs or TBs of data BUT it is a fucking EMPTY cluster!! I'm still testing the service...
  • 1
    355d
    you reeeeally need mongodb compatibility? maybe DynamoDB could be a better fit, if you need elasticity that frequently.
  • 0
    355d
    @JsonBoa I really need it :-(
  • 0
    355d
    Backend connectors should be, in the case of databases, relatively easy to replace. I believe it's a matter of the right libraries.

    AWS is a mistake, like any PCP.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment