On 05/23/15 11:40, Mark Joslin wrote:
Hi Michael, thanks for the tips. I believe that would be a bit
overkill for this project though it would seem fun. I've decided to
take a pretty minimalistic approach:
* Start two seed nodes on AWS
* Have all the API servers connect to the cluster via these seed nodes
* Have all API servers create 1 master actor on the cluster (and
maintain a reference to it) which has a router actor underneath it
of worker actors
Simply said, every API server has one master that lives on the cluster
and each master has a router of max 5 worker actors underneath it. I'm
under the assumption jobs get distribute among the cluster in some
sort of intelligent fashion. Please let me know if I'm under the wrong
assumption.
this isn't very clear to me, perhaps a some ascii box art would help?
regarding job distribution, i think you have the wrong assumption. if
you are taking a minimalistic approach, then it is *you* who is building
the intelligence :)
However, I'm still a bit confused when it comes to splitting the play
project up. I have a play project with 4 sub-modules underneath it,
but I only want one of the modules. I imagine I can go about this in a
few different ways:
* Turn the one sub-module into a git repo itself and then reference
it via git submodules
o One - Regular backend that contains all the submodules but now
contains a git reference
o Two - Seed server that contains git submodule
* Package the entire play backend (with submodules) into a jar and
copy over to seed server git repo configuration. Treat it more as
an artifact. This seems faster, but I had trouble referencing my
class files doing this in a test project
Anyway, I'm sure I'll figure things out but appreciate any tips.
not knowing anything about your project layout, i would suggest creating
artifacts and shipping those to servers. in that way you know that each
server is bit-for-bit the same. not a new idea but it has a new popular
term: 'immutable infrastructure':
http://chadfowler.com/blog/2013/06/23/immutable-deployments/
-Michael
--
Read the docs: http://akka.io/docs/
Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
