Re: [akka-user] Pub/Sub reality check - Java and Scala

[Jonas Boner]

Is it all in-memory? If so, I'll go with Akka EventBus. Can't beat the
simplicity of that.
If not, alt 2 sounds most straight forward. Less hassle with
infrastructure setup and maintenance.

On Fri, Aug 3, 2012 at 9:20 PM, RBH Dev <rbh...@gmail.com> wrote:
> Here's my line of thinking on implementing PubSub from both Scala/Akka and
> Java based clients and I'm looking for some pure, unadulterated honest
> feedback.
>
> Background:
>
> * We have multiple independent Akka (1.x) based REST service apps.
> * We have multiple web based MVC framework (Java) based apps with REST
> endpoints.
>
> When an Akka based service app receives a change request, both MVC framework
> apps and Akka based REST service apps might need to know. To me, this is
> PubSub.
>
>
> Ways to solve (in no particular order):
>
> 1) zeromq clients in both MVC and Akka services
> 2) POST/PUT updates via http to various REST endpoints. Fire-and-forget.
> 3) Zookeeper clients
> 4) akka event bus? - add akka jar(s) to MVC framework apps.
>
> To start, our requirements are fairly simple, so I'm wary of heavyweight
> solutions. I'm strongly leaning towards 2. The URLs used in 2 will point
> to load balancer as we have multiple instances of everything running. So,
> with hardware based load balancer, we get the routing/clustering.
>
> Thoughts? Opinions?
>
> Thanks in advance,
> Todd
>
> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/akka-user/-/zf1DhCGKRjQJ.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.



--
Jonas Bonér
CTO
Typesafe - The software stack for applications that scale
Phone: +46 733 777 123
Twitter: @jboner