On 06.05.14 06:56, Matthew Howard wrote:
Our design is still a bit young, but we're going with a work pulling
pattern right now... which is something that has worked well for me in
the past (this is my first Akka impl though). In terms of the overall
approach of using a queue/datastore
I thought reactive applications were all event-based and, in particular,
events could be generated and flow through an application from GUI back to
GUI.
Does the way Akka Persistence Views work prevent this (since they are, if I
understand correctly, essentially polling for events)?
Can
I wouldn't be surprised if there were also some good options using Akka
alone. On top of my large queue concerns with Rabbit I didn't particularly
feel like adding another component into the mix if I didn't need to. I
wouldn't be shocked if you could do something pretty cleanly with just
On 06.05.14 08:18, Ashley Aitken wrote:
Hi Martin,
Thank you for your response to my questions.
On Tuesday, 6 May 2014 13:13:46 UTC+8, Martin Krasser wrote:
Finally, I believe I would like to track all the events that get
added to the entire journal (treating it like a combined
I believe Martin may have kindly answered, at least part of, this question
in another thread.
If I may paraphrase him: the way Akka Persistence Views work currently
(polling) is an implementation detail and later versions of Akka
Persistence may provide a push-based approach as well.
If
On 06.05.14 08:59, Ashley Aitken wrote:
I believe Martin may have kindly answered, at least part of, this
question in another thread.
If I may paraphrase him: the way Akka Persistence Views work currently
(polling) is an implementation detail and later versions of Akka
Persistence may
On Tuesday, 6 May 2014 15:18:29 UTC+8, Martin Krasser wrote:
The availability of (new) events in the journal is also an event. Whether
a view is actively notified about their availability (= push) or if the
view tries to find out itself (= pull) is rather a technical detail. A
pull-based
I'm doing some testing on remote lookup and dead watch. Therefore I use an
actor (see below) which simple resolves a given address and in the case we
got an actor-path back we start to watch them.
When writting the sample I made a type and forgot the @ between the IP
address and the
On 06.05.14 09:31, Ashley Aitken wrote:
On Tuesday, 6 May 2014 15:18:29 UTC+8, Martin Krasser wrote:
The availability of (new) events in the journal is also an event.
Whether a view is actively notified about their availability (=
push) or if the view tries to find out itself (=
Hello,
I am seeing this log message from akka.
2014-05-06 10:42:20 akka.actor.OneForOneStrategy SEVERE : Some(null) (of
class scala.Some)
I am using *Akka 2.2.3* and no, I can't upgrade. It's not my decision. I
also can't show the code. Sorry.
I have some clue about which actor is involved,
Hello Hakkers,
today I am interested how you usually configure your bundles inside an OSGi
container.
I can easily access the application.conf provided with Akka itself to get
to all the default values. I can also provide bundle specific configuration
in separate files and my bundle would
hi,
I am Nicola (not Christian),
I created a github repo for you:
https://github.com/pic/akkaTheHutt
you have three classes:
FiniteStateMachine ( no persistence, extends Actor )
AlmostPersistentFSM ( extends Processor but no use of Persistent )
PersistentFSM ( persistence )
The only
Hello Endre,
What about one actor from each node joining the DistributedPubSubMediator
and this actor could register with a node local Akka eventbus? The sharded
actors could register with the local Akka event bus for messages.
So a message published to a topic, on the
Hi Jabbar,
We were thinking of that same design. If you implement before we do, please
share your experiences with that design and we will do the same.
Chanan
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Hello Hakkers,
following this discussion, I have made some progress in getting an actor
based API around the OSGI framework going.
For those interested, the project is located at [1]. There is some
documentation at [2] - [4].
[1] https://github.com/woq/de.woq.osgi.java
[2]
Hello Chanan,
This is an evening project for me so you might get it done before me.
Although I got the cluster sharding, with cassandra, working last night.
On Tuesday, 6 May 2014 14:14:19 UTC+1, Chanan Braunstein wrote:
Hi Jabbar,
We were thinking of that same design. If you implement
I'm the author of the blog post from Conspire you referenced. In our case,
losing the supervisor isn't a problem because all work is generated from a
SQL database. If the supervisor crashes, we can just start over. Our
worker nodes subscribe to cluster event notifications and will queue
6 maj 2014 kl. 17:38 skrev Ryan Tanner ryan.tan...@gmail.com:
I'm the author of the blog post from Conspire you referenced. In our case,
losing the supervisor isn't a problem because all work is generated from a
SQL database. If the supervisor crashes, we can just start over. Our
Thanks again Martin.
On Tuesday, 6 May 2014 14:37:48 UTC+8, Martin Krasser wrote:
Good so I am on the write track. I am confused a little about the Views
keeping stage in memory and with snapshots. What state would this be?
Surely the read model itself is maintaining most of the state,
Thanks Martin.
On Tuesday, 6 May 2014 15:53:28 UTC+8, Martin Krasser wrote:
On 06.05.14 09:31, Ashley Aitken wrote:
Reactive I take to mean push, the events are driving action in the system,
from GUI to GUI.
From a user's (= API) perspective, a View will always receive Persistent
Which tools do you use to visualise your running Akka system?
I know that the Typesafe Console can be used, but is that still being
developed?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Hello there,
The Console is in deed EndOfLife-ing.
The Typesafe Activator is on it’s way to support more and more actor tracing
etc. Currently it does a little bit already, though it’s currently not a
production solution.
Thanks to EOLing the console multiple community projects have appeared
I'm using Kamon in production with the docker image kamon/grafana-graphite.
You should check
http://kamon.io/teamblog/2014/04/27/get-started-quicker-with-our-docker-image/
Cheers,
Sergio Magnacco
Despegar.com
El martes, 6 de mayo de 2014 15:52:36 UTC-3, Konrad Malawski escribió:
Hello
Why not use a business-level identity as a correlation id that travels
through the processing and view compositions that you describe? In the end
you could use an EventBus to tell a given presentation that its newly
composed view is available. You might find your answers using something
like
Thanks for the input! I will have a look at both tools.
Den tirsdag den 6. maj 2014 20.41.40 UTC+2 skrev Anders Bech Mellson:
Which tools do you use to visualise your running Akka system?
I know that the Typesafe Console can be used, but is that still being
developed?
--
Read the
Hi I was trying to implement an router which could router a message to an
specified routee via the message's key.just as the ConsistentHashRouter.
when I look at the selected method ,the comes out routees are in an
immutable seq,but not a mapString,Routee,so if I want to selected one of
the
On 06.05.14 19:10, Ashley Aitken wrote:
Thanks Martin.
On Tuesday, 6 May 2014 15:53:28 UTC+8, Martin Krasser wrote:
On 06.05.14 09:31, Ashley Aitken wrote:
Reactive I take to mean push, the events are driving action in
the system, from GUI to GUI.
From a user's (= API)
On 06.05.14 18:21, Ashley Aitken wrote:
Thanks again Martin.
On Tuesday, 6 May 2014 14:37:48 UTC+8, Martin Krasser wrote:
Good so I am on the write track. I am confused a little about
the Views keeping stage in memory and with snapshots. What state
would this be? Surely the
On 06.05.14 20:52, Vaughn Vernon wrote:
Thanks. I still think that the docs need to be strengthened to state
that the Processor will not work unless it receives a Recover message,
and that the Recover message could take several forms depending on the
recovery goals.
I agree. Do you want to
On 06.05.14 21:13, Matthew Howard wrote:
On Tuesday, May 6, 2014 2:06:16 AM UTC-4, Martin Krasser wrote:
You may be interested in this pull request
https://github.com/akka/akka/pull/15036 that enables reading
from akka-persistence journals via reactive-stream
30 matches
Mail list logo
