Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Akka User List
Home
+ new post
About this group
Join this group
Pub/Sub reality check - Java and Scala
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
RBH Dev  
View profile  
 More options Aug 3 2012, 3:20 pm
From: RBH Dev <rbhd...@gmail.com>
Date: Fri, 3 Aug 2012 12:20:18 -0700 (PDT)
Local: Fri, Aug 3 2012 3:20 pm
Subject: Pub/Sub reality check - Java and Scala
Print | Individual message | Show original | Report this message | Find messages by this author

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 must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jonas Boner  
View profile  
 More options Aug 9 2012, 5:49 am
From: Jonas Boner <jo...@jonasboner.com>
Date: Thu, 9 Aug 2012 11:49:25 +0200
Local: Thurs, Aug 9 2012 5:49 am
Subject: Re: [akka-user] Pub/Sub reality check - Java and Scala
Print | Individual message | Show original | Report this message | Find messages by this author
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.

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

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google