Ranter
Join devRant
Do all the things like
				++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
				Sign Up
			Pipeless API
 
				From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
				Learn More
			Comments
		
- 
				
				 asgs109202yis it because the provisioning of the 3rd shard is slow? Or there is a huge amount of data to relocate? asgs109202yis it because the provisioning of the 3rd shard is slow? Or there is a huge amount of data to relocate?
- 
				
				@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...
- 
				
				 JsonBoa31232yyou reeeeally need mongodb compatibility? maybe DynamoDB could be a better fit, if you need elasticity that frequently. JsonBoa31232yyou reeeeally need mongodb compatibility? maybe DynamoDB could be a better fit, if you need elasticity that frequently.
- 
				
				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






 Then they say
Then they say
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