Akka has nice UDP support and is accessible from Java or Scala.
Implementing with Akka Actors is attractive for scale - even if scale won't be a big issue for awhile. I'd like to "do it right" where possible. Scala V.S. Java - what do you guys think?
There also seems to be some akka-persistence bits for SimpleDB - but docs seem hard to find (maybe in the scaladocs?).
It's an open question to the team whether we try to have a single Spring Data based @Repository codebase shared across the UI and UDP server. But we do need to come up with a how we're going to manage the code:
Another option is to just use Netty + Spring (including Spring Data @Repository we're currently implementing)
If its Akka/Scala I see a seperate repo and SBT based build (more tooling fun!). Do we add it as a git submodule to the UI if there's shared code?
If straight Java we could just add a subfolder and a subproject Gradle build to create another deployable
Initial thoughts:
Handling UDP
Akka has nice UDP support and is accessible from Java or Scala.
Implementing with Akka Actors is attractive for scale - even if scale won't be a big issue for awhile. I'd like to "do it right" where possible. Scala V.S. Java - what do you guys think?
There also seems to be some akka-persistence bits for SimpleDB - but docs seem hard to find (maybe in the scaladocs?).
It's an open question to the team whether we try to have a single Spring Data based @Repository codebase shared across the UI and UDP server. But we do need to come up with a how we're going to manage the code:
Another option is to just use Netty + Spring (including Spring Data @Repository we're currently implementing)
Share your thoughts team.
Ron