Viewing profile — tomasol
tomasol
HN member- Joined
- Thu, Mar 09, 2023, 5:28 PM UTC
- HN karma
- 383
- Public activity
- 30 items
- HN profile
- View on Hacker News ↗
About tomasol
No profile information was provided.
Recent public activity
-
comment
Comment #48912557
Really cool, the page is noticeably snappier. I'm wondering why they don't put the database on a network-attached block volume. DigitalOcean offers Volumes Block Storage, which is …
- story
-
comment
Comment #48345294
Subscribe to this issue: https://github.com/obeli-sk/obelisk/issues/65
-
comment
Comment #48338205
sorry about that, I do love Beatles!
-
comment
Comment #48338170
Check out https://obeli.sk/blog/comparing-dbos-part-1/
-
comment
Comment #48338144
Hi, I wrote a comparison blog post between Obelisk and the Java version of DBOS a couple of months ago: https://obeli.sk/blog/comparing-dbos-part-1/
- story
- story
-
comment
Comment #47832457
I believe the codegen must be separated from the runtime. Every time you ask AI for a new task, it must be deployed as a separate app with the least amount of privileges possible, …
- story
-
comment
Comment #46127511
fsync is the most expensive operation during a write. NORMAL mode means you don't care whether last ~100 ms of transactions before a process crash / VM restart are going to be pers…
-
comment
Comment #46126968
Author is setting PRAGMA synchronous="normal", meaning fsync is not issued as part of every write tx, but eventually. In order to make the comparison fair it should be set to "full…
- story
- story
- story
- story
- story
-
comment
Comment #43651931
Sorry for the late reply. The actual order in which child workflows finish and their results hit the persistence layer is indeed nondeterministic in real-time execution. Trying to …
-
comment
Comment #43642735
> Just create a race condition among a join set. All responses and completed delays are stored in a table with an auto-incremented id, so the `-await-next` will always resolve to t…
-
comment
Comment #43642602
Thanks for bringing that up. Regarding the NaN canonicalization, there is a flag for it in wasmtime [1], I should probably make sure it is turned on. Although I don't expect to be …
-
comment
Comment #43642535
I can do that. Please create an issue if you want to be notified about it.
-
comment
Comment #43641270
The structured concurrency paradigm in workflows is stricter to what I'm reading here [1]. The whole execution model is different from the Task [2], as workflows are transparently …
-
comment
Comment #43639439
Indeed. I cannot compare the implementations as flawless is not open source. However on a high level they both share the same philosophy. I believe the biggest difference is that O…
-
comment
Comment #43639120
> I was referring to the workflows, that is, writing the workflows in managed languages, not the activities. Ah understood. I have no plans supporting native workflow executors. > …
-
comment
Comment #43638874
> do I also need to compile activities to WASM Yes, currently all activities must conform to the WASI 0.2 standard. This is the simplest for deployment, as you only need the obelis…