In general, I personally would avoid going to fully managed “customized” solution as it could result in vender lock-in, which is kind of AWS’s whole business model.

It usually costs very little when starting, and it might actually cost them money to provide you the service, but ends up costing a whole lot more if you get to scale pass a point, where they end up getting back their money.

That being said, if you don’t plan to scale past a certain point and is not worried about possibly having to migrate to another service when they inevitably increase their pricing, you should be good.

I agree about AWS/Cloud in general but this is managed Postgres so you can always take your backups and run. Postgres is quite possibly the only database left that we can say for certain won’t be rugpulled, which is why we all use it!

@VictorGaiva .. I agree, seems better to implement and manage sharding at application level so I can avoid vendor lock. This way, I can still use regular migration commands for Ecto.

Besides that, to even start using the Amazon Aurora PostgreSQL Limitless Database, there is a minimum requirement of running 16 ACU / Hour service, which is around 2,200 USD / Month! To just start using managed sharding