Simple (simplistic?) solution: don’t send the large object, send its URI and
have one of the clustered actors pick it up.
Regards,
Roland
> 2 nov 2015 kl. 23:28 skrev Kostas kougios :
>
> I am looking for an efficient way to broadcast a case class only once to my
> akka cluster, i.e. broadcas
To be honest I don't know how good the java port is.
/Patrik
tis 3 nov. 2015 kl. 01:45 skrev Gary Wu :
> Hi Patrik,
>
> Is the Java port of leveldb still intended for testing only? We would
> like to use Akka Persistence on some architectures that don't yet have
> native leveldb libraries (i.e. A
it is not an option as the actors have to react based on the large
object's data. Only one of them will reply, based on that data
On 03/11/15 12:24, Roland Kuhn wrote:
Simple (simplistic?) solution: don’t send the large object, send its
URI and have one of the clustered actors pick it up.
Reg
This might not be very nice, but you could pre-serialize your large
object to a akka.util.ByteString. Serialization of an
akka.util.ByteString should be much cheaper than serializing a large.
complex data structure. I am assuming that the serialization overhead
is what you want to avoid.
On Mon, N
Hi Patrik,
Sorry for the late response, I must've missed the notification about your
reply or something.
Anyway, I'll open an issue for this and try to see if I can do it myself.
Thanks,
Tal
On Monday, October 19, 2015 at 1:31:01 PM UTC+3, Patrik Nordwall wrote:
>
> SharedLeveldbJournal.setSto
I assume serialization is optimal, but still the data size will be large.
Maybe UDP multicast (
http://doc.akka.io/docs/akka/2.4.0/scala/io-udp.html#UDP_Multicast ) is
what I need, though I need to dig in a bit to the docs to understand
how it works
On 03/11/15 13:42, Rüdiger Klaehn wrote:
UDP is limited to 65507 Bytes. Might be a bit small for large messages...
I assume serialization is optimal, but still the data size will be large.
Maybe UDP multicast (
http://doc.akka.io/docs/akka/2.4.0/scala/io-udp.html#UDP_Multicast ) is
what I need, though I need to dig in a bit to the docs
transmit only once would imply 100% lossless communication, which does not
exist afaik?
--
Cheers,
√
On 3 Nov 2015 18:07, "Rüdiger Klaehn" wrote:
> UDP is limited to 65507 Bytes. Might be a bit small for large messages...
> I assume serialization is optimal, but still the data size will be larg
oh
maybe breaking the msg into parts but it seems too much of a trouble
On 03/11/15 17:07, Rüdiger Klaehn wrote:
UDP is limited to 65507 Bytes. Might be a bit small for large messages...
I assume serialization is optimal, but still the data size will be large.
Maybe UDP multicast (
http
Hi,
We at NextGenTel have been using Event Sourcing with Akka Persistence since
approximately Akka 2.3.2 and are now mostly using 2.3.14 and some 2.4.0.
It started out with just one App (micro service using Dropwizard) but we
now have ~6 different apps using it.
All the apps are using clustering
Thanks for sharing!
We'd love to hear more about your experiences with Akka Persistence—what's
great and what's not-so-great, in case you are able and willing to share
that :)
On Tue, Nov 3, 2015 at 10:51 PM, Morten Kjetland wrote:
> Hi,
>
> We at NextGenTel have been using Event Sourcing with
Publishing to topic with Distributed PubSub will only transfer the message
once per node that has any subscribers.
However, how large is large? Akka remoting is not designed for large
messages, so you should consider splitting it up in parts or use another
side channel, such as http or Akka IO.
/
12 matches
Mail list logo
