5 ms·
Yet another half-baked and poorly supported AWS service. Now that they’re starting to see pressure on their margins I’d love to see AWS focus on their core prod
by woeirua 4y ago
Yet another half-baked and poorly supported AWS service. Now that they’re starting to see pressure on their margins I’d love to see AWS focus on their core products, but instead we get more spun off side projects.
- bob1029 4y ago> I’d love to see AWS focus on their core products Agreed. I used to be all-in on the AWS experience, but it has really fallen behind in my opinion. Azure is quickly gobbling up their product scope per my preferences. The only things that are standing strong are Route53 (because Azure doesn't offer domain registration), and S3 (because I'm too lazy to learn something else). For example, the current UX around S3 makes me really nervous. I felt like I was authorizing the release of radiological material when setting up a new public bucket.
- dragonwriter 4y ago> I’d love to see AWS focus on their core products, Scope of coverage is an AWS selling point
- darksaints 4y ago100%. My own personal infuriating example: Postgres RDS takes way too long to roll out new versions, major or minor, even those with important security fixes. Their upgrade processes fail when you use PostGIS, so every major version upgrade is a massive undertaking (clone the database locally, upgrade the database locally, drop all objects from the existing RDS, upgrade the RDS, then restore from local). And while their latest versions have relatively recent extensions, those extensions are upgraded carelessly (e.g. PostGIS is on 3.3.2, but the underlying geos library hasn’t been upgraded for several years, and most of the new PostGIS features rely on the newer geos versions). It has gotten so bad we’ve been considering running Postgres on our kubernetes cluster. I can’t imagine the headaches being any worse.