hmaxdml

5 ms·

31.
by hmaxdml 1y ago
It is an evolution. The DBOS workflow orchestrator places a DB at the center of your application to handle most of the complicated state management problems.
32.
by hmaxdml 1y ago
Thanks for posting! I am one of the author, happy to answer any question!
33.
by hmaxdml 1y ago
:wave: Hey there, I'm working on the Go library and just wanted to confirm your suspicion: "since Golang doesn't have decorators in the same way Python does, we still have to have code doing the kind of "manual callback&
34.
Bye bye 3 way handshake(billatnapier.medium.com)
22 points by hmaxdml 1y ago|5 comments
35.
by hmaxdml 1y ago
It is very good at doing the job that people over-eagerly offload to specialized services. Queues, notifications, scheduled jobs. And can be specialized with extensions.
36.
by hmaxdml 2y ago
It is a library you import to annotate your code. Most APIs do have a service layer that need some form or orchestration. This library makes the service layer automatically orchestrated. Your workers too can import the library and have embe
37.
by hmaxdml 2y ago
Thanks for the suggestion! One way would be to drop a note on discord. Otherwise there is a contact form https://www.dbos.dev/contact .
38.
by hmaxdml 2y ago
All processes use Postgres as a reference, so they can learn about pending workflows in need of recovery. The DBOS library handles concurrency management under the hood, such that only 1 process can work on a workflow at a given time.
39.
by hmaxdml 2y ago
Would be nice if there was a serverless library that lets you do in-process orchestration so you don't need abominations like Step Functions ;) e.g., https://github.com/dbos-inc/durable-swarm
40.
by hmaxdml 2y ago
Agreed that existing serverless stacks like lambda are a nightmare. But the real problem is that they don't solve the state management problem. (You need step functions to compose lambdas AND you need a bunch of custom logic for recove
41.
by hmaxdml 2y ago
What's your favorite orchestration solution for this kind of lightweight task?
42.
by hmaxdml 2y ago
That was before DBOS -- the serverless platform that bills you only for CPU time, not wall clock time ;) see https://www.dbos.dev/blog/aws-lambda-hidden-wait-costs
43.
by hmaxdml 2y ago
Replace lambda by DBOS and you'll cut down the cost by 15x, at least, and save you a lot of time developing (SAML sucks)
44.
by hmaxdml 2y ago
Can you give us some more details about the CD pipeline you built? :)
45.
by hmaxdml 2y ago
Yes, its normal Python/node.js so you an use all their packages. We know of users running puppeeter to scrap data.
46.
by hmaxdml 2y ago
I wouldn't equate the lambda UX with "serverless" at large. I work on a serverless system that runs the same code you upload (e.g, python). You write it as a traditional API then upload it to the cloud and done. One thing tha
47.
by hmaxdml 2y ago
Step functions are an "external orchestrator". With DBOS your orchestration runs in the same process, so you can use normal testing frameworks like pytest for unit tests. Its super easy to test locally.
48.
by hmaxdml 2y ago
One of the motivation for DBOS is that OSes were designed with orders of magnitude less state to manage than today. (e.g. linux >30 years ago). What's made to manage tons of state? A DBMS! :)
49.
by hmaxdml 2y ago
Today you have to write all the observability code to export telemetry from your app. Telemetry should be emitted, formatted and exported automatically by web/cloud development frameworks. disclaimer: I am the author of the article
50.
Observable by Default with OpenTelemetry(dbos.dev)
3 points by hmaxdml 2y ago|1 comments
51.
by hmaxdml 2y ago
The SDKs -- which do most of the heavy lifting of managing state for you -- are open source. For example the TS SDK ( https://github.com/dbos-inc/dbos-transact ) runs on node and you can run node anywhere (k8s, VMs, etc.
52.
by hmaxdml 2y ago
But that's the reason why serverless has mostly failed so far -- because it is not stateful. And that is only because most existing offering don't have the correct primitives. By that I mean that if the programming model has a way
53.
by hmaxdml 2y ago
In terms of money it might end up cheaper for the infra itself (especially if it runs in your garage) In term of your personal time, well, you'll not grow a business on it without hiring people to maintain it or spend a lot of time doi
54.
by hmaxdml 2y ago
Well its problem is that you still have to... install the entire thing. Whatever serverless means, it should allow programmers to focus on their code, not on the platform. Like, at all.
55.
by hmaxdml 2y ago
You need nested virtualization, which many VMs support -- it is architecture dependent. But, yes, to maximize the benefits you'll want to run on baremetal. From the standpoint of a cloud user, the kind that likes Dokku, the experience
56.
by hmaxdml 2y ago
I liked Dokku when I was still happy using docker, but since I started working on https://www.dbos.dev/ , I value microVMs way more. The problem with Dokku is that, while its easy to use if you have experience in devops, wel
57.
by hmaxdml 2y ago
This idea that serverless is "just" for scalability is a misconception and pessimism about the future of computing. What serverless should really mean is that you focus on your code and you don't configure your digital ocean,