|
|
|
|
|
by etothet
46 days ago
|
|
There are many reasons to dislike AWS and many reasons to stay away from it (and the criticisms in the article about support resonate with me), but a few things in the article stood out to me as a bit misleading: First, the comparison of running an Anthropic model in Bedrock vs. Claude Code is not apples-to-apples. With Bedrock pay API pricing (or whatever negotiated pricing AWS and the vendor agreed to), just like the other providers in Bedrock. You know what else is more expensive/token than a Claude Code subscription? API access for pretty much all of the other big providers. Whether we like it or not, Anthropic sees subscrition usage as different than API usage. This is not at all an AWS thing. Second, regarding Lambda: the cold start criticism is fair but for heavy workloads usually isn't an issue and for light workloads there are some workarounds. But, if you have a discreet function that can exist outside of your app, Lambda still may be a better option here. As far as the "MASSIVE development complexity" I wish the author cited specifics. I feel like this can be true of any technology and depends on how you go about setting it up and implementing it. I've used Lambda for all sorts of use cases, including a full web application (I'd advise staying away from this one!) and there definitely is a sweet spot where it can work well. Lastly, the whole bit about using AWS WorkMail would also suggest they never really "left" AWS. But maybe I misunderstood that part as I'm not very familiar with that service. |
|