[HN Gopher] Show HN: DBOS - Transactional Serverless for TypeScr...
___________________________________________________________________
Show HN: DBOS - Transactional Serverless for TypeScript Apps
Hello HN! We're excited to show you DBOS, a transactional
serverless SDK and platform that makes it easy to write fault-
tolerant, observable, and scalable TypeScript applications. We're
a startup commercializing research we did at Stanford and MIT.
(https://dbos-project.github.io/). The main idea behind DBOS is to
store EVERYTHING about your application in the database. This gives
you some unique features: * Reliable execution - Your program's
execution state is stored in the database, so if it's ever
interrupted, it automatically resumes from where it left off
without repeating any work already performed. * Time travel -
Every change to your program's state is recorded in the database,
so you can "rewind" time and restore the state of your application
to what it was at any point in the past. For example, time travel
debugging-take a tricky bug in production, rewind time, and
reproduce it locally on your laptop. Today, we released our open-
source SDK (https://github.com/dbos-inc/dbos-ts) and our free-to-
try serverless platform (https://www.dbos.dev/dbos-cloud). We'd
love for you to try them out and let us know what you think!
Here's a quick guide to get you started:
https://docs.dbos.dev/getting-started/ We're here to answer any
questions!
Author : KraftyOne
Score : 34 points
Date : 2024-03-12 20:59 UTC (1 days ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| catzapd wrote:
| Good to see alternatives coming up to ridiculously complex
| serverside programming frameworks like SpringBoot, Node, etc etc.
| jghn wrote:
| Did you come before or after the other DBOS[1] ?
|
| [1] https://dbos-project.github.io
| otoburb wrote:
| Evidently it's the same project, but your link was the
| "research & publish" phase of the project, while this
| announcements seems to be the "commercial" phase.
|
| The same list of people who wrote the blog post(s) on your
| research/publish link are listed as co-founders[1] on the
| commercial site.
|
| [1] https://www.dbos.dev/about
| jghn wrote:
| Huh, you're right. It did seem coincidental that just
| yesterday I saw something hyping Stonebreaker's new DB
| Operating System concept.
| qianli_cs wrote:
| Hello! @otoburb is right (thanks!). We are the same group
| commercializing our DBOS research.
| bahador wrote:
| I browsed the documentation and saw no references to provisioning
| database compute/memory resources. Is the persistence serverless,
| autoscaling, and scale to zero?
| achanda358 wrote:
| https://docs.dbos.dev/getting-started/quickstart-cloud#provi...
| bahador wrote:
| Yes but it says nothing about cpu/ram and/or
| memory/storage/io optimized hardware, cost per hour, or
| anything like that. Does it scale to zero? Does it autoscale?
| Will it throttle with spikes in load?
| KraftyOne wrote:
| Thanks for the good question! Our free tier offers fixed
| resources per application (under the hood, a Firecracker
| microVM with 512 MB of RAM and 1 vCPU) that scale to zero
| when not in use. For paid users, we'll offer autoscaling
| per application--we'll share more details on that soon.
| ibgeek wrote:
| I love the idea, especially from reproducibility and debugging
| standpoints.
|
| It seems like there would be a significant performance hit, even
| if doing this on a single machine.
|
| If the application does external I/O, it seems impossible to
| reproduce state if it depends on the state of an external system.
|
| Can you give more details on the pros and cons and your ideas for
| ideal use cases?
|
| Thanks!
| qianli_cs wrote:
| Thanks for your interest in DBOS! We talk more about how things
| work on this docs page: https://docs.dbos.dev/explanations/how-
| workflows-work For functions doing database transactions, we
| record execution information in that transaction, which isn't
| much overhead. For functions that communicate with external
| services, we record their output in the database and use the
| recorded output during recovery and debugging. We think DBOS is
| especially valuable for applications where reliability or
| security is a major concern (for example, in financial services
| or insurance).
___________________________________________________________________
(page generated 2024-03-13 23:02 UTC)