3 ms·
IMO AWS once you get off the core services is full of beta services. S3, Dynamo, Lambda, ECS, etc are all solid. But there are a lot of services they have that
by ecshafer 11mo ago
IMO AWS once you get off the core services is full of beta services. S3, Dynamo, Lambda, ECS, etc are all solid. But there are a lot of services they have that have some big rough patches.
- BOOSTERHIDROGEN 11mo agoLightsail fortunately behave like core services.
- kentm 11mo agoI'd add SQS to the solid category. But yes, the less of a core building block the specific service is (or widely used internally in Amazon), the more likely you are to run into significant issues.
- nextworddev 11mo agoKinesis is decent
- hnlmorg 11mo agoThis. 100 times this.
- jeffparsons 11mo agoRDS, Route53, and Elasticache are decent, too. But yes, I've also been bitten badly in the distant past by attempting to rely on their higher-level services. I guess some things don't change. I wonder if the difference is stuff they dogfood versus stuff they don't?
- ozten 11mo agoA big problem for a when three AWS teams launch the same thing. Lowers confidence in dogfooding the “right” one.
- smallmancontrov 11mo agoOr when your AWS account rep is schmoozing your boss trying to persuade them to use something that is officially deprecated, lol.
- raw_anon_1111 11mo agoAmazon Connect is a solid higher level offering. But only because it is a productized version of Amazon Retail’s call center
- phantasmish 11mo agoI once used one of their services (I forget which, but I think it was there serverless product) that “supported” Java. … but the official command line tools had show-stopper bugs if you were deploying Java to this service, that’d been known for months, and some features couldn’t be used in Java, and the docs were only like 20% complete. But this work-in-progress alpha (not even beta quality because it couldn’t plausibly be considered feature complete) counted as “supported” alongside other languages that were actually supported. (This was a few years ago and this particular thing might be a lot better now, but it shows how little you can trust their marketing pages and GUI AWS dashboards)
- nunez 11mo agoI'm assuming you're talking about Lambda. I don't mess with their default images. Write a Dockerfile and use containerized Lambdas. Saves so many headaches. Still have to deal with RIE though, which is annoying.
- nunez 11mo agoMy understanding is that AWS productizes lots of one-offs for customers (like Snowball), so that makes sense
- belter 11mo ago>But there are a lot of services they have that have some big rough patches. Enlight us...
- kentm 11mo agoPersonally, EMR has never shaken off the "scrappy" feeling (sometimes it feels OK if you're using Spark), and it feels even more neglected recently as they seem to want you on AWS Glue or Athena. LakeFormation is... a thing that I'm sure is good in theory if you're using only managed services, but in practice is like taking a quick jaunt on the Event Horizon. Glue Catalog has some annoying assumptions baked in. Frankly the entire analytics space on AWS feels like a huge mess of competing teams and products instead of a uniform vision.
- deleted 11mo ago[deleted]
- weird-eye-issue 11mo agoTrue with Cloudflare too. Just stick with Workers, R2, Durable Objects, etc...
- plantain 11mo agoNot even sure about R2 with it's unpredictable latencies.
- weird-eye-issue 11mo agoHmm is it actually that bad? Keep in mind r2 is only stored in one region which is chosen when the bucket is first created so that might be what you're seeing But I've never really looked too closely because I just use it for non-latency critical blob storage