tqwewe

8 ms·

1.
Show HN: Hekla, an event sourcing runtime with its own language(hekla.tqwewe.com)
1 points by tqwewe 7d ago|0 comments
2.
by tqwewe 11mo ago
I haven't put any effort into any kind of snapshotting capabilities yet, since I won't want the scope to be too large and there's often ways of designing your system in ways where replaying isn't a big issue (the db scan
3.
by tqwewe 11mo ago
Yes exactly, I heard from an existing KurrentDB customer that the weird licensing change was actually a deal breaker causing them to move away from KurrentDB despite the migration pains. I think a community, open source built project in Rus
4.
SierraDB: A distributed event store built in Rust(tqwewe.com)
74 points by tqwewe 11mo ago|13 comments
5.
Comparing Rust Actor Libraries: Actix, Coerce, Kameo, Ractor, and Xtra(theari.dev)
2 points by tqwewe 2y ago|0 comments
6.
Building a Rust-Powered Event Store from Scratch: Meet Eventus(theari.dev)
1 points by tqwewe 2y ago|0 comments
7.
by tqwewe 2y ago
This is resolved now :) Added better material around distributed actors.
8.
by tqwewe 2y ago
I've added an indepth section to the kameo book about actor registration and lookup, including how it works: https://docs.page/tqwewe/kameo/distributed-actors/registerin...
9.
by tqwewe 2y ago
I've added an indepth section to the kameo book about distributed actors if you'd like to read more. https://docs.page/tqwewe/kameo/distributed-actors
10.
by tqwewe 2y ago
Great question, I did some digging into the source code of beam to help answer if signals should have special priority, and the conclusion (with the help of someone else from the elixir community) was that signals have no special priority o
11.
by tqwewe 2y ago
Thanks for the reply! The example you gave does make sense regarding the stage being used with the actors startup method. I wasn't aware async_trait wasn't needed, thats nice to see. Also congrats on it being used in such a big co
12.
by tqwewe 2y ago
In the case of tokio, multiple actors can run on a single thread. Tokio uses a worker pool of threads equal to the number of cores on your system. So spawning a new actor will run amongs other actors. This lets us perform io operations in a
13.
by tqwewe 2y ago
Under the hood it uses tokio runtime. So as long as you enable `rt-multi-thread` feature flag in tokio, and use `#[tokio::main]`, then yes! Actors can run on multiple threads. By default tokio uses worker threads, equal to the number of thr
14.
by tqwewe 2y ago
Would be absolutely awesome I agree! But, sadly I don't think tokio really runs in wasm just yet. But I see it being possible some day
15.
by tqwewe 2y ago
It's a nice point. I am a fan of the beam runtime, and it has been an influence on the design decisions of kameo. However I don't see myself switching to another language from Rust anytime soon, especially with the amazing advance
16.
by tqwewe 2y ago
Actix was built initially using its own runtime and has gone over many iterations including a runtime change to tokio over its lifetime. In the past, building asynchronous actors with actix has been a huge pain and felt like a big after tho
17.
by tqwewe 2y ago
Thank you for the lovely feedback! Happy to hear this. Will continue improving documentation, adding more examples to code docs, etc.
18.
by tqwewe 2y ago
Not yet, however I hope to answer with yes soon. I'm using kameo heavily in a startup I'm building (oddselite.app). Hopefully will be released shortly for this to be a yes. But as of now, it's still quite a new library and th
19.
by tqwewe 2y ago
Yeah I definitely need to add some more documenation on this feature!
20.
by tqwewe 2y ago
Thanks! Definitely agree with you, I'll create an issue for this
21.
by tqwewe 2y ago
Thanks! Its definitely missing, I'll need to add that perhaps to the kameo book. Its using libp2p under the hood with Kademlia distributed hash table for actor registrations.
22.
by tqwewe 2y ago
Hi, I'll probably need to add better documentation on the internals of how remote actors work. There's not really any special features for informing other actors when one is registered currently, but you could do this yourself of
23.
by tqwewe 2y ago
In my experience, setting up gRPC often involves a lot of boilerplate, particularly with code generation when using libraries like Tonic. While gRPC is great for well-defined, schema-driven communication, one of the big advantages of distri
24.
Show HN: Kameo – Fault-tolerant async actors built on Tokio(github.com)
105 points by tqwewe 2y ago|58 comments