TrueTeller

3 ms·

1.
Claude Code uses WebFetch vs. WebSearch (observations, schemas, prompts)(mikhail.io)
2 points by TrueTeller 1y ago|0 comments
2.
by TrueTeller 5y ago
(Pulumi providers dev here) This has been the case in the past but we are investing in our provider ecosystem. We built several first-party native providers that aren't based on TF: Kubernetes, Azure, Google. Now, we also encourage thi
3.
InfiniCache: Distributed Cache on Top of AWS Lambda (Paper Review)(mikhail.io)
5 points by TrueTeller 7y ago|0 comments
4.
by TrueTeller 8y ago
Hi, the author here. It's a good point and a valid concern, but I did an explicit choice here: I didn't want to make the article longer. I have a prequel post which describes my thinking of why durable functions make sense, includ
5.
by TrueTeller 8y ago
"Analysis" is not that hackernews-worthy :P
6.
by TrueTeller 8y ago
IMO, every greenfield app that can benefit from "just focus on your business code" model. P.S. I'm the author of OP, thanks for reading!
7.
by TrueTeller 8y ago
That's all plausible except the price issue. Say, you keep 10 containers alive, so you make 10x 100ms calls every 5 minutes. That's gonna be $0.20 per month. 20 cents.
8.
by TrueTeller 8y ago
Yes, one could prewarm N instances by sending N parallel requests every 5 minutes. You have to know N though :) For most apps, scale-out cold start won't be too much of a deal breaker: longer instance lifetime + shorter start will do t
9.
by TrueTeller 8y ago
There are some, e.g. https://github.com/jeremydaly/lambda-warmer and my post https://mikhail.io/2018/08/aws-lambda-warmer-as-pulumi-compo...
10.
by TrueTeller 8y ago
1. Most applications don't need the warm-up since they aren't too critical to cold starts. 2. Cloud vendors are working and succeeding to make cold starts faster, and AWS is at the forefront. 3. Pre-warming done right is extremely