2 ms·
"What’s the problem (with Elasticache)? It is expensive, and no one notices for months." So you just click on stuff without knowing how much it costs? Really?
by raverbashing 7y ago
"What’s the problem (with Elasticache)? It is expensive, and no one notices for months."
So you just click on stuff without knowing how much it costs? Really?
> Secondly that cache.* prefix means this instance costs $0.216/hr instead of $0.126/hr, a 71.4% premium. Then you might think you need one for dev, qa, and prod
Ok and you pick a cache of the same size for dev/qa/prod? Again, really?
> But, not all data/records/events should go into Kinesis. It is not a general purpose enterprise event bus or queue.
Yes, there's SQS for that. But it seems another case of clicky-go-lucky. "Hey it says queue here so we'll just use this right?!"
> Lambdas are great for the following tasks:
Yes, agreed. I would generalize it as: it is good for specific small tasks, especially when plugging into the rest of the AWS infrastructure (reacting to/from SQS, S3 events, etc)
> Lambda is horrible for:
> A replacement for REST API endpoints.
Sigh
General advice: if something feels weirdly hard, then you're probably doing it wrong.