It doesn't really match the error message, but your "driver" entry looks a
bit off to me - shouldn't that just be the driver class name?
I think the ";databaseName=" would be attached to the
URL part, not the driver. And the 3 before the ";", I don't know..
On Monday, November 13, 2017 at
if deadline exceeded.
>
> /Patrik
>
> lör 11 nov. 2017 kl. 16:52 skrev lutzh <lutz.h...@gmail.com
> >:
>
>> Hi mailing list,
>>
>> I was wondering if anyone had some good ideas about this. Say I have an
>> actor that receives data from some sensor
I think the samples just aren't meant to be run like that, i.e. the message
is right, there is no runnable class.
You can still study the source code, and you can run the multi-node tests
by entering:
> multi-jvm:test
Hth,
Lutz
Am Montag, 6. November 2017 18:00:07 UTC+1 schrieb Nagaraju
Hi Michael,
Don't throw out Akka HTTP just yet, do your own measurements first. With
maybe the exception of high frequency trading, I think you'll be ok...
Am Freitag, 10. November 2017 13:32:14 UTC+1 schrieb Michael Zhong:
>
> That's awful, I've recently start using akka-http to write some
Hi Jakub,
I can't download the zip file (I*m using the web interface, it tells me
"The requested document, benchmark.zip (0x38bdd40db96ca part 0.1), could
not be found: DOCID_NOT_FOUND")
Could you maybe share the sources on Github, Bitbucket or the likes?
Thanks,
Lutz
Am Freitag, 11.
Hi mailing list,
I was wondering if anyone had some good ideas about this. Say I have an
actor that receives data from some sensor, once an hour. I'm using Akka
Cluster Sharding and Akka Persistence. So the message arrives, Akka will
take care of restoring the actor state, processing the
wrote:
>
> Hi Lutz,
>
> On Tue, Oct 10, 2017 at 11:33 AM, lutzh <lutz.h...@gmail.com
> > wrote:
>
>>
>> eventsByTag in the CassandraReadJournal uses a materialized view to read
>> the events. It can be configured to ignore the latest events (events
>&
eventsByTag in the CassandraReadJournal uses a materialized view to read
the events. It can be configured to ignore the latest events (events
younger than "eventual-consistency-delay") to give the materialized view
some time to converge.
This seems to work well enough for most cases, if the "
ilable anywhere?
>
> On Friday, 24 March 2017 16:53:59 UTC+5:30, lutzh wrote:
>>
>>
>> > I am interested in knowing if Distributed Data for Service Locator is
>> used in any of the projects you know of, and to know any lessons learnt.
>>
>> There's a
> I am interested in knowing if Distributed Data for Service Locator is
used in any of the projects you know of, and to know any lessons learnt.
There's a talk "Service Discovery with Akka Replicated Data" by Jeroen
Gordijn that you might find interesting:
On Tuesday, 31 January 2017 16:17:53 UTC+1, José González Gómez wrote:
>
> Hi!
>
> I've been reading about Akka persistence, and it seems the way to go to
> persist data in a reactive application, using event sourcing and immutable
> data models. I have no experience doing this, so I'd love to
,
Lutz
On Wednesday, 25 January 2017 17:08:50 UTC+1, Felipo Gonzale wrote:
>
> Hi lutzh,
>
> The idea about using the Cluster Singleton came as a way to "have a single
> entry point to an external system". Right now the microservices(each
> service is an akka cluster) expose
Sounds great, looking forward to trying out the δ-CRDTs. Kudos to the Akka
team/contributors!
On Thursday, 26 January 2017 10:37:37 UTC+1, Patrik Nordwall wrote:
>
> Dear hakkers,
>
> we—the Akka committers—proudly present the first development milestone for
> Akka 2.5. Since the release of
Hi Felipo,
>From what you describe, it doesn't sound like your, let's call it API
gateway, needs to be a singleton, and I don't think a cluster singleton is
"usually the way to go" for this. Why do you need it to be a singleton,
resp. what benefit are you looking for?
On Wednesday, 25
I hear Akka in Action https://www.manning.com/books/akka-in-action is
pretty good. Apparently you can read the first 3 chapters for free if you
sign up for the newsletter on the Lightbend
website: https://www.lightbend.com/resources/e-books
Hope this helps,
Lutz
On Thursday, 19 January
I'm not familiar with these libraries, but a curious person...
acid-state - how would you say it compares to Akka persistence, or event
sourcing in general? To me it seems it tries to achieve exactly the same
thing, only it calls the events functions and the journal the history log.
vcache -
Hi Haddock,
Fibers as such do not prevent you from blocking. Pretty much like in Akka,
if you use blocking I/O you block the underlying thread, which is then of
course not available for other fibers or actors. So async I/O it is.
The fibers approach to it is to provide a FiberAsync wrapper,
o see 1st answer
here:
http://stackoverflow.com/questions/27734816/does-scala-offer-async-non-blocking-io-when-working-with-files)
Am Dienstag, 27. Oktober 2015 14:15:43 UTC+1 schrieb Haddock:
>
>
>
> Am Dienstag, 27. Oktober 2015 11:24:21 UTC+1 schrieb lutzh:
>>
>> Hi
Hi Jacobus,
If you can look behind the somewhat provocative title, I think Eberhard
Wolff gives a pretty comprehensive overview of why you should look beyond
app servers in Java Application Servers Are Dead:
http://jaxenter.com/java-application-servers-dead-1-111928.html
19 matches
Mail list logo
