https://github.com/johnmurray/romeo

https://github.com/johnmurray/romeo

Last synced: about 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/johnmurray/romeo
• Owner: JohnMurray
• Created: 2018-06-23T20:20:25.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2018-07-29T14:12:08.000Z (over 6 years ago)
• Last Synced: 2024-11-21T05:40:16.195Z (2 months ago)
• Language: Rust
• Size: 70.3 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        

# Romeo [![Crates.io](https://img.shields.io/crates/v/romeo.svg?style=flat-square)](https://crates.io/crates/romeo) [![Travis](https://img.shields.io/travis/JohnMurray/romeo.svg?style=flat-square)](https://www.travis-ci.org/JohnMurray/romeo)

Romeo is an experimental actor framework for Rust. At this point things are really

rough and I'm still getting things ready for eventual use. So go away. `-__-`

## More Information

Still here? Okay, well I'll keep talking. The eventual goal is to create a

distributed actor framework with plug-able behaviors. What do I mean by that?

Well, firstly the goal is to get something that _can_ run on multiple machines

and communicate across them. But once we get to this point, there are a lot of

questions about how the distributed system should be built. What guarantees do

I want to provide? How do I shard? How do I replicate? How do I get consensus

and what do I need consensus on?

This project intends to make all of that plug-able so that user-defined implementations

can be used and experimented with. The goal is to create an actor system that is

customizable/tunable to the end-users desires.

Like I said at the beginning, this is currently just in the beginning phases of me

designing the basic bits and getting everything _working_. Don't expect magic at the

moment, or any real stability if you plan to play around with it. 

## Latest Progress

Actors can be created, addressed, and communicated with. A basic runtime exists to

execute messages over actors. The runtime operates schedulers across multiple threads,

each running a simplified event-loop.

## Currently Working On

Implementing a basic context with actor self-management features (stop, restart, etc).