31–33 of 33 posts
Earlier quoted context omitted.
Care to elaborate or link to your thoughts? Temporal has always been on my radar. I wanted to do a deeper dive, but the cost seems pretty high for the managed service.
Good concept, buggy implementation. That’s not ok for a distributed system that glues together important pieces of your product.
These docs don’t fill me with confidence. That’s… weird given who’s behind the project. What gives? > Workflows provide the following reliability guaranteees: > 1. They always run to completion. You can’t guarantee that. > 2 […] Regardless of what failures occur during a workflow's execution, it executes each of its transactions once and only once. “Executed” is the wrong word here, if the database goes down half way…
Author here--thanks for the feedback! We'll update the docs to clarify the first three points assume that the database and application always restart and return online if they go offline. For the last point, we'll clarify we mean that the code of the workflow function must be deterministic. For example, a workflow shouldn't make an HTTP GET request and use its result to determine what to do next, even though that's t…
is it just me or am i seeing less and less serverless showing up in roles? seems like there was a big rush during the hype around 2021, and people went back to ec2/kubernetes
That is because that is exactly what happened. It was tried, people went too far and tried to build entire applications in FaaS and it was largely unsuccessful. Cue a bunch of migrations onto k8s to contain costs and get back control over process lifetime, better integration with existing monitoring/tracing, etc, etc. I am probably the farthest from a fan of serverless but I have developed some appreciation for all t…