How does this compare with akka ( http://akka.io )?
Akka & Ordasity have somewhat different goals and each takes a different approach. Apple/Oranges.
Ordasity: Building Stateful Clustered Services on the JVM
11–20 of 20 posts
Re: Ordasity: Building Stateful Clustered Services on the JVM
#12How does this compare with akka ( http://akka.io )?
Much like our engineers, our software is extremely opinionated. Ordasity, Scalang, and Overlock are all small, extremely focused libraries to solve a single problem in a single way. This is quite similar to the Unix philosophy and we have found it to be similarly successful. Projects like Akka take a more maximalist, all-encompassing approach that doesn't work well for the way we build and operate services.
One love,
Lil' B
Re: Ordasity: Building Stateful Clustered Services on the JVM
#13What are the other types that can be applied to workUnit in the startWork? It would be ideal to support Thrift protocol transports too
We have no plans to support Thrift.
Re: Ordasity: Building Stateful Clustered Services on the JVM
#14Why is this better than Hadoop?
Re: Ordasity: Building Stateful Clustered Services on the JVM
#15Why is this better than Hadoop?
I don't want to live on this planet anymore.
Re: Ordasity: Building Stateful Clustered Services on the JVM
#16I'm not very familiar with building services on the JVM at the moment (though I'd love to be), so a quick, honest question: What are the pros/cons of Ordasity[1] vs. something like Finagle[2]? Are they comparable and if so why would one be chosen over the other, what are the strengths of one vs the other, etc. [1]: https://github.com/boundary/ordasity [2]: https://github.com/twitter/finagle
Hey Mitchell, Thanks for asking -- in short, the use cases are a bit different. Finagle is a framework for building asynchronous RPC systems (e.g., services or APIs with transports over HTTP or Thrift), and Ordasity is a library for cluster membership, load balancing, and distribution. Twitter's put together a nice toolkit atop Netty for building reliable services and describing communication between them. These serv…
Let me propose a use case, and I would appreciate if you indicated if I'm totally off base.
A virtual world, where actors(users) interact with each other, with the cluster providing validation and consistency between actors over a dynamic geography, where each node in the cluster would be handling the realtime requests of actors that are capable of interacting with each other, distant actors would be on different nodes.
(Would this work for a distributed server infrastructure to say an large online game?)
Re: Ordasity: Building Stateful Clustered Services on the JVM
#17Re: Ordasity: Building Stateful Clustered Services on the JVM
#18How does this compare with akka ( http://akka.io )?
Much like our engineers, our software is extremely opinionated. Ordasity, Scalang, and Overlock are all small, extremely focused libraries to solve a single problem in a single way. This is quite similar to the Unix philosophy and we have found it to be similarly successful. Projects like Akka take a more maximalist, all-encompassing approach that doesn't work well for the way we build and operate services. One love,…
The ordasity of your leftist signature, sir.
Re: Ordasity: Building Stateful Clustered Services on the JVM
#19How "Load-based workload balancing" is done in JDK?
If you're curious about Ordasity's load balancing strategies, check out Section 4: "Distribution / Coordination Strategy" in the docs: https://github.com/boundary/ordasity The code is also fairly straightforward to follow if you'd like to take a glance in the repo as well.
Thank you, I thought that you somehow found a way to measure CPU load of java processes, in fact you leave end user to measure the work load in end users units.
Re: Ordasity: Building Stateful Clustered Services on the JVM
#20I'm not very familiar with building services on the JVM at the moment (though I'd love to be), so a quick, honest question: What are the pros/cons of Ordasity[1] vs. something like Finagle[2]? Are they comparable and if so why would one be chosen over the other, what are the strengths of one vs the other, etc. [1]: https://github.com/boundary/ordasity [2]: https://github.com/twitter/finagle
Hey Mitchell, Thanks for asking -- in short, the use cases are a bit different. Finagle is a framework for building asynchronous RPC systems (e.g., services or APIs with transports over HTTP or Thrift), and Ordasity is a library for cluster membership, load balancing, and distribution. Twitter's put together a nice toolkit atop Netty for building reliable services and describing communication between them. These serv…
How does it compare to Norbert: http://sna-projects.com/norbert/ ?