Hacker News new | ask | show | jobs
by JustinGarrison 680 days ago
What services would you get rid of?
2 comments

A huge portion of AWS services are really annoying in my opinion to grassroots developers and platform managers because they are basically executive demoware.

You know the kind where the salesman comes in and in front of the CIO builds some whiz-bang demo and like 20 minutes and has a CEO asking why it takes a month or more to do equivalent stuff by real it workers.

And sometimes it's worse to customize the out-of-the-box solution than just creating your own solution. For some AWS products, it's pure pain to get it up and running in the configuration you require. There are edge cases and bugs to worry about.

That whiz-bang demo? Maybe that's the only functionality that works right. Maybe it's all using default values that won't pass your internal security and compliance policies.

And lets not forget the pain of integrating something new with existing systems. It's easy to show a demo of something that doesn't integrate with existing systems, and just show a slide or two of what things it integrates with.

Doesn't Amazon/AWS use this very heavily? Whenever we have to get on a call with AWS engineers it's through Chime.

As a product, it seems fine. I'm not entirely sure it's an area AWS really needed to have a competitor, but now that they do, /shrug

At every org I've had to interface at a deep level with AWS, they've used our Zoom. n=1
If you get rid of chime you also get rid of slack huddles (built on Chime). Like many AWS services the backend of Chime is good, the UX/UI is terrible.
TIL, interesting design decision on Slack's part.
It was a business decision because slack's old /call command was built on a startup they aquired. I don't know the details but I'm sure Amazon gets deep discounts on slack and slack get's the same for chime.

https://slack.com/blog/news/slack-aws-drive-development-agil...