The best way implementing queue in akka
1,014 views
Skip to first unread message
Erwin k
Apr 27, 2012, 9:51:48 AM4/27/12
to akka...@googlegroups.com
Hello All,
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.
The other way is to use akka.dispatch.MessageQueue.
Your insight would be appreciated.
Thanks in advance,
Erwin
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.
The other way is to use akka.dispatch.MessageQueue.
Your insight would be appreciated.
Thanks in advance,
Erwin
Björn Antonsson
Apr 28, 2012, 2:03:57 AM4/28/12
to akka...@googlegroups.com
On Friday, 27 April 2012 at 15:51, Erwin k wrote:
Hello All,
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.
Hi Erwin,
I'm note really sure what you are trying to implement? If you have a consumer that is an actor, then the producer can just send messages to the consumer and they are enqueued in that actors MailBox, which is backed by a MessageQueue .
If you are looking for durability that survives a node crash, then akka supports durable mailboxes http://doc.akka.io/docs/akka/2.0.1/modules/durable-mailbox.html
The other way is to use akka.dispatch.MessageQueue.
The trait akka.dispatch.MessageQueue is not something you can use directly, you need a class that implements it. I don't know why you would use that yourself though, since it is used internally by the actor anyway.
B/
Your insight would be appreciated.
Thanks in advance,
Erwin
--
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/-/Mj6kec5jb6sJ.
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.
Erwin k
Apr 28, 2012, 3:50:21 AM4/28/12
to akka...@googlegroups.com
Hello Bjorn,
Thank you a lot for your reply.
I'd like to implement generic infrastructure Event Bus (Pub/Sub) utility lib for our customer.
Actually, we prefer that our customer will not mess with actors but only with our infrastructure/service.
We would like to develop above infrastructure for many divisions that use our service.
We have used AKKA Event Bus for our Pub/Sub requirement and the AKKA Listener package for our broadcast requirement.
One of our requirement is queue data structure, one application on JVM put message in the queue, other application on the same JVM start and takes this message from queue (i.e the producer at first time put the message and then the consumer consumes the message).
So for the queue implementation (i.e. first publisher then producer) I'd like to use akka also, but i have some dilemma about the implementation.
Your insight/directions would be appreciated.
Erwin
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
Thank you a lot for your reply.
I'd like to implement generic infrastructure Event Bus (Pub/Sub) utility lib for our customer.
Actually, we prefer that our customer will not mess with actors but only with our infrastructure/service.
We would like to develop above infrastructure for many divisions that use our service.
We have used AKKA Event Bus for our Pub/Sub requirement and the AKKA Listener package for our broadcast requirement.
One of our requirement is queue data structure, one application on JVM put message in the queue, other application on the same JVM start and takes this message from queue (i.e the producer at first time put the message and then the consumer consumes the message).
So for the queue implementation (i.e. first publisher then producer) I'd like to use akka also, but i have some dilemma about the implementation.
Your insight/directions would be appreciated.
Erwin
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Friday, 27 April 2012 at 15:51, Erwin k wrote:Hello All,
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.Hi Erwin,I'm note really sure what you are trying to implement? If you have a consumer that is an actor, then the producer can just send messages to the consumer and they are enqueued in that actors MailBox, which is backed by a MessageQueue .If you are looking for durability that survives a node crash, then akka supports durable mailboxes http://doc.akka.io/docs/akka/2.0.1/modules/durable-mailbox.htmlThe other way is to use akka.dispatch.MessageQueue.The trait akka.dispatch.MessageQueue is not something you can use directly, you need a class that implements it. I don't know why you would use that yourself though, since it is used internally by the actor anyway.B/
Your insight would be appreciated.
Thanks in advance,
Erwin
--
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/-/Mj6kec5jb6sJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+unsubscribe@googlegroups.com.
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Friday, 27 April 2012 at 15:51, Erwin k wrote:Hello All,
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.Hi Erwin,I'm note really sure what you are trying to implement? If you have a consumer that is an actor, then the producer can just send messages to the consumer and they are enqueued in that actors MailBox, which is backed by a MessageQueue .If you are looking for durability that survives a node crash, then akka supports durable mailboxes http://doc.akka.io/docs/akka/2.0.1/modules/durable-mailbox.htmlThe other way is to use akka.dispatch.MessageQueue.The trait akka.dispatch.MessageQueue is not something you can use directly, you need a class that implements it. I don't know why you would use that yourself though, since it is used internally by the actor anyway.B/
Your insight would be appreciated.
Thanks in advance,
Erwin
--
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/-/Mj6kec5jb6sJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+unsubscribe@googlegroups.com.
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Friday, 27 April 2012 at 15:51, Erwin k wrote:Hello All,
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.Hi Erwin,I'm note really sure what you are trying to implement? If you have a consumer that is an actor, then the producer can just send messages to the consumer and they are enqueued in that actors MailBox, which is backed by a MessageQueue .If you are looking for durability that survives a node crash, then akka supports durable mailboxes http://doc.akka.io/docs/akka/2.0.1/modules/durable-mailbox.htmlThe other way is to use akka.dispatch.MessageQueue.The trait akka.dispatch.MessageQueue is not something you can use directly, you need a class that implements it. I don't know why you would use that yourself though, since it is used internally by the actor anyway.B/
Your insight would be appreciated.
Thanks in advance,
Erwin
--
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/-/Mj6kec5jb6sJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+unsubscribe@googlegroups.com.
On Saturday, April 28, 2012 9:03:57 AM UTC+3, Björn Antonsson wrote:
On Friday, 27 April 2012 at 15:51, Erwin k wrote:Hello All,
What is the best way to implementing message QUEUE with akka.
Producer insert message in queue, when the consumer will start it'd consume the message.
IMHO, one way is to manage map in producer with id and when the consumer start it will provide the last id that it consumed to the producer and the producer return all messages produced after that id.Hi Erwin,I'm note really sure what you are trying to implement? If you have a consumer that is an actor, then the producer can just send messages to the consumer and they are enqueued in that actors MailBox, which is backed by a MessageQueue .If you are looking for durability that survives a node crash, then akka supports durable mailboxes http://doc.akka.io/docs/akka/2.0.1/modules/durable-mailbox.htmlThe other way is to use akka.dispatch.MessageQueue.The trait akka.dispatch.MessageQueue is not something you can use directly, you need a class that implements it. I don't know why you would use that yourself though, since it is used internally by the actor anyway.B/
Your insight would be appreciated.
Thanks in advance,
Erwin
--
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/-/Mj6kec5jb6sJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+unsubscribe@googlegroups.com.
Björn Antonsson
Apr 30, 2012, 2:17:00 AM4/30/12
to akka...@googlegroups.com
On Saturday, 28 April 2012 at 09:50, Erwin k wrote:
Hello Bjorn,
Thank you a lot for your reply.
I'd like to implement generic infrastructure Event Bus (Pub/Sub) utility lib for our customer.
Actually, we prefer that our customer will not mess with actors but only with our infrastructure/service.
We would like to develop above infrastructure for many divisions that use our service.
We have used AKKA Event Bus for our Pub/Sub requirement and the AKKA Listener package for our broadcast requirement.
One of our requirement is queue data structure, one application on JVM put message in the queue, other application on the same JVM start and takes this message from queue (i.e the producer at first time put the message and then the consumer consumes the message).
SInce you say that the second application should "get" messages from the queue, I'm assuming that you don't want callbacks to happen when messages arrive, but you want a more polling API.
If you are talking about a queue with with a direct exchange and no fanout then I would just go with a plain java.util.concurrent.ConcurrentLinkedQueue as the backing data structure.
B/
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/KomaQyuZj6EJ.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
--
Erwin k
Apr 30, 2012, 2:54:15 AM4/30/12
to akka...@googlegroups.com
Thanks a lot for your reply.
We need to think about generic solution.
We need to think about generic solution.
Reply all
Reply to author
Forward
0 new messages