Newbie Spellweaver
- Joined
- Jul 13, 2015
- Messages
- 71
- Reaction score
- 31
Oreo Emulator [Kotlin/Netty/Cassandra/Post-Shuffle]
Hello frenz! About months ago I felt want creating a new project, solely for educational purposes. That's why I started this project bleh
What should it be?
Oreo (Google s2) is a cross-platform Habbo emulator, written entirely in Kotlin. I prefered use kotlin than java, because is more concise (POJO in a single line, singleton object) and some enterprise are moving to it, like Pinterest and Evernote.
My first aim is make a really stable and scalable emulator with total code coverage. I don't mind having all features from the original product. The SWF revision will be the PRODUCTION-201707041014-428081343, no particular reason.
And about actors?
By the way I won't use the actor model (discussion about on page two). On my researches I proved that actors is really effective for backend servers, it can handle about 160k requests per second. Some graphs from Microsoft Orleans:
But it isn't the most practical solution for a retro and there isn't need for it. So I will be using the traditional architecture.
Cassandra
And you didn't read wrong. I've been working with Cassandra in a startup on the last months, and it's been great. Cassandra employs many mechanisms for fault tolerance and the administration is easy, since is a homogenous system.
Then I'm 70% sure that oreo will use cassandra.
I created the thread in order to make contributions possible, then feel free to contribute! and you can expect a regular inactivity because I'm on high school. Nonetheless, I hope that the thread stays open for some time.
Checkout the repository:
Regards,
Guilherme Araújo
Hello frenz! About months ago I felt want creating a new project, solely for educational purposes. That's why I started this project bleh
What should it be?
Oreo (Google s2) is a cross-platform Habbo emulator, written entirely in Kotlin. I prefered use kotlin than java, because is more concise (POJO in a single line, singleton object) and some enterprise are moving to it, like Pinterest and Evernote.
My first aim is make a really stable and scalable emulator with total code coverage. I don't mind having all features from the original product. The SWF revision will be the PRODUCTION-201707041014-428081343, no particular reason.
And about actors?
By the way I won't use the actor model (discussion about on page two). On my researches I proved that actors is really effective for backend servers, it can handle about 160k requests per second. Some graphs from Microsoft Orleans:
But it isn't the most practical solution for a retro and there isn't need for it. So I will be using the traditional architecture.
Cassandra
And you didn't read wrong. I've been working with Cassandra in a startup on the last months, and it's been great. Cassandra employs many mechanisms for fault tolerance and the administration is easy, since is a homogenous system.
Then I'm 70% sure that oreo will use cassandra.
I created the thread in order to make contributions possible, then feel free to contribute! and you can expect a regular inactivity because I'm on high school. Nonetheless, I hope that the thread stays open for some time.
Checkout the repository:
You must be registered to see links
Regards,
Guilherme Araújo
Last edited: