Akka Persistence may very well provide you some helpful ideas and insights.
>From a pure perspective - it sounds as though you very much do want things
to be blocking and serial. Are you aware that you can specify the execution
context that actors run in and can in fact limit these so that many
uggestion "min number of clustered instances in
> application.conf == your cluster size - but this only works if you have
> statically sized clusters."
>
>
>
> On Thursday, November 30, 2017 at 3:52:57 PM UTC+2, Daniel Stoner wrote:
>>
>> Hi Dobrin,
>>
> Cluster Singleton node.
>
> By supported I mean that Aggregates can now be spread across the cluster
> (and not sitting on the oldest node like when using cluster singletons) and
> also you cannot get the same Aggregate/actor on more then one cluster node
> at a time even during split
I would second Konrads suggestion of going with the Cassandra version. I
have had great experiences with that, and the AWS DynamoDB community
version (Albeit it lacked a lot of features and we ended up porting our own
version and bug fixing/extending it. Surprisingly this ended up being a lot
e
Hi Kraythe,
Perhaps it helps to see a real world example that we've been working on -
with a good number of routes involved.
This is from our AkkaHttpServer class. It's job is to inject all the routes
(ordersV2, searchv3, searchTerms, persistence) which consist of around 6
actual endpoints per
I guess you have to remember that Akka-HTTP originates from Spray - and so
those choices were likely already made. (I'm sure there is a fully
plausible performance threading reason that is beyond me too hehe).
Well I know how i'd do nesting in Java at least if its any help.
Implementing a custo
I think perhaps your mistaking the same mistake I did when I first picked
up Akka HTTP coming from a background with Jersey.
What I wanted to do - was nest paths inside of each other thinking:
path("v1") {
path("orders") {whatever}
path("customers") {whatever}
}
Would be the perfect syntax for se
uch complex and generalised code. Perhaps the Scala equivalent
syntax is more manageable but I was very tempted to go back to allowing the
failures on the DB to occur during startup and try to put in something more
basic in terms of custom throttling.
Thanks kindly,
Daniel Stoner
On Thursday, 14
In my organisation we had quite a number of problems with Cluster
quarantine behaviour both in AWS and on our own local PCs (We launched a
cluster of 5 actor systems during test so that tests emulated as closely as
possible our intended production environment).
What we found was that quarantine
Beware that if you don't handle serialisation failures as rejection - then
you can easily get into a state whereby another actor keeps sending a
message that simply will not serialise when persisted. Your only awareness
of this will be the log errors that might occur in your JournalImpl and
you
the serialisation-bindings and other
assorted config working. EG You just
utilise SerializationExtension.get(system).serialize(entity).
Thanks kindly,
Daniel Stoner
--
Daniel Stoner | Senior Software Engineer UtopiaIT | Ocado Technology
daniel.sto...@ocado.com | Ext 7969 | www.ocadotechnology.com
; .filter(msg -> msg.equals(5))
> .runForeach(System.out::println, materializer)
However this returns a CompletionStage representing the runForEach's
completion without result.
A pointer in the right direction would be hugely appreciated.
Thanks,
Daniel St
e then you simply do not deliver the message to yourself and
hence perform no action.
I'm keen to point out that whatever message you deliver to yourself you
should not persist if you follow this second pattern.
Thanks kindly,
Daniel Stoner
On Wednesday, 22 June 2016 08:33:36 UTC+1, Daniel
in EG /user/someRandomX which no longer
exists after a restart?
In which case the only sensible path to send to would seem to be the
sharded actor itself - EG I should follow a pattern of:
deliver(self().path(), .)
Thanks kindly,
Daniel Stoner
--
Daniel Stoner | Senior Software Engineer Utopi
TH_PARAM_MAJOR_VERSION)
> .slash(PATH_MINOR_VERSION)
> .slash(PATH_PARAM_MINOR_VERSION)
This only made sense to me after someone happened to randomly show me their
Spray API from a while back :) Having never used Spray in Scala I've found
it quite difficult to guess what you can do where.
Thanks ki
gt; (orderId, majorVersion, minorVersion)-> doSomeBusinessThing
Thanks in advance!
Daniel Stoner
--
Daniel Stoner | Senior Software Engineer UtopiaIT | Ocado Technology
daniel.sto...@ocado.com | Ext 7969 | www.ocadotechnology.com
--
Notice: This email is confidential and may contain cop
e to write some kind of mixed
Marshaller/Business pojo to HttpResponse mapper.
PetClinic link:
https://github.com/akka/akka/blob/v2.4.6/akka-http-tests/src/main/java/akka/http/javadsl/server/examples/petstore/PetStoreExample.java
Thanks hugely!
Dan
--
Daniel Stoner | Senior Software Enginee
to ship it in 2.4.5 which is just a few days away
> actually.
>
> --
> Konrad Malawski
>
> From: Daniel Stoner
> Reply: Daniel Stoner
> Date: 20 April 2016 at 14:02:21
> To: Konrad Malawski
>
> CC: akka-user@googlegroups.com
>
> Subject: Re: [akka-use
Hi Konrad/Others,
I notice that Github issue was taken over into:
https://github.com/akka/akka/pull/20088 and has not made it yet into v2.4.4.
Is it on the roadmap for 2.4.5 or is there any update about plans for this?
Thanks kindly,
Daniel Stoner
On 15 February 2016 at 16:00, Konrad Malawski
some obvious solutions that we will carry out - for instance we
should manually down the nodes. But it does seem peculiar that when
removing an old incarnation of a node it 'seemingly' quarantines the new
incarnation.
Thanks kindly,
Daniel Stoner
On 25 February 2016 at 10:57, Danie
y - is there a way we can see the ActorSystems uid to confirm this is
the case, and finally is there some way we can specify the uid used (to
enforce uniqueness)?
Thanks kindly,
Daniel Stoner
--
Daniel Stoner | Senior Software Engineer UtopiaIT | Ocado Technology
daniel.sto...@ocado.com | Ext 7969 |
o invest heavily into the existing JavaDSL.
>
> I'll give your exact need a closer look a bit later to see how we cover it
> in the new DSL.
>
> --
> Cheers,
> Konrad 'ktoso’ Malawski
> Akka <http://akka.io> @ Typesafe <http://typesafe.com>
>
c at the
top of the route tree rather than repeat it constantly in all the bottom
leaves.
Thanks kindly,
Daniel Stoner
--
Daniel Stoner | Senior Software Engineer UtopiaIT | Ocado Technology
daniel.sto...@ocado.com | Ext 7969 | www.ocadotechnology.com
--
Notice: This email is confidential and may
When we first began using AKKA we had a similar approach and decided to put
all the business logic in a service layer. This is a pretty standard Spring
practice and it made testing a doddle - and also meant we could start
writing the logic before we'd confirmed our favourite AKKA architecture.
people do with regards populating their seed node
list in Amazon.
Thanks kindly,
Daniel Stoner
--
Daniel Stoner | Senior Software Engineer UtopiaIT | Ocado Technology
daniel.sto...@ocado.com | Ext 7969 | www.ocadotechnology.com
--
Notice: This email is confidential and may contain copyright
It may well not be the cause in your situation, but if you want to rule out
serialisation troubles - turn on the following options in application.conf:
akka{
actor{
serialize-creators = on
serialize-messages = on
}
}
This will force your application to attempt to serialise everything that
passe
26 matches
Mail list logo
