5 ms·
This looks really nice! Curious if its running in production anywhere
by __erik 2y ago
This looks really nice! Curious if its running in production anywhere
- qwertox 2y agoI agree, really nice syntax. There's a limitation mentioned in the docs: While messages are processed sequentially within a single actor, Kameo allows for concurrent processing across multiple actors. which is justified via This [sequential processing] model also ensures that messages are processed in the order they are received, which can be critical for maintaining consistency and correctness in certain applications. I agree to this and it gives the library a well defined use. Docs and examples are well made.
- zackangelo 2y agoThis limitation is common to most implementations of the actor model. In fact, I think a lot of people would consider it a feature, not a limitation because it allows you to reason about your concurrent behavior in a more straightforward way.
- tqwewe 2y agoThank you for the lovely feedback! Happy to hear this. Will continue improving documentation, adding more examples to code docs, etc.
- rad_gruchalski 2y ago> There's a limitation It’s a feature.
- tqwewe 2y agoNot 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 the API has gone through many breaking changes to get where its at now