HackerTrans
トップ新着トレンドコメント過去質問紹介求人

sunny--tech

no profile record

投稿

[untitled]

1 ポイント·投稿者 sunny--tech·2 年前·0 コメント

[untitled]

1 ポイント·投稿者 sunny--tech·3 年前·0 コメント

Reviving Httpstatuses.com (Now: Httpstatuses.io)

jkulton.com
3 ポイント·投稿者 sunny--tech·4 年前·0 コメント

コメント

sunny--tech
·3 年前·議論
“OP uses a sledgehammer to build a bird house and complains it’s too difficult”

This is equivalent to using K8s to deploy a static site and complaining infra is the hardest of all. React isn’t the skeleton key for front end apps. Sometimes using simpler tools is the way to go and adding complexity when it becomes necessary
sunny--tech
·3 年前·議論
I ran a 5000 character essay that was mainly generated by GPT4 and lightly edited by me through that and it reported 99.98% human lol
sunny--tech
·4 年前·議論
The company I work at runs a HA setup of Temporal on K8s, so Temporal atop k8s is a great recipe. I'd be curious to hear the reasoning for Temporal replacing K8s (or do you just mean replacing a piece of k8s?) Seeing as how as reconciliation is just a tool it uses for it's container orchestration, not sure Temporal would replace that but an interesting idea nonetheless.
sunny--tech
·4 年前·議論
It still boggles my mind that, in an age where K8s is huge and K8s's reconciliation loop pattern is well recognized, Temporal has yet to put "reconciler" or "state-machine" in their documentation or descriptions.

I say this as someone who loves using Temporal and see a big future for them.

Temporal is a managed state-machine. If you're familiar with K8s, you can think of it as a dedicated reconciler. Plain and simple.

Do you want a resource to go from one state to another (i.e. user orders food -> food is delivered) regardless of transient errors and other hiccups? Temporal handles the plumbing of driving your resource to it's desired end state.

Do you have a workflow that has multiples steps? Can anyone of those steps fail for whatever reason and you'll need to figure out how to do retrying/cleaning up? Temporal handles that.

Essentially you can write your business logic without the worry of including the (often) boilerplate retry, cleanup, scheduling, etc logic. If you're familiar with K8s reconciliation and how it retries failed operations again and again until it reaches the goal, it's much like that.

Temporal can do much more than that, but that's its bread and butter and I'm trying to describe it simply so that people can understand. It is a bit of a paradigm shift and has a bit of a learning curve when you first start using it.

But like others have said, it's very powerful.