A couple of years ago I was a newbie in Akka, by newbie I mean I didn't
know anything and I had to deliver a project in a new job:
*A distributed and high available trading system for a financial
institution.*
My concurrency and Riak knowledge background helped me to understand how
Akka works but what helped me the most was reading the first 3 chapters of
the Akka documentation reference,
we can give you ideas but how are you going to be able to
understand/implement them without knowing some Akka fundamentals?
I strongly suggest you to start with the following:
- *Introduction:*
http://doc.akka.io/docs/akka/2.4.12/intro/index-java.html
- *General:* http://doc.akka.io/docs/akka/2.4.12/general/index.html
- *Actors:* http://doc.akka.io/docs/akka/2.4.12/java/index-actors.html
- You can for now skip Futures and Agents or you can read it too.
- *Networking:*
http://doc.akka.io/docs/akka/2.4.12/java/index-network.html
- *Utilities* *-optional, some other aspects explained here-*
: http://doc.akka.io/docs/akka/2.4.12/java/index-utilities.html
There is a PDF version of the whole documentation which is what I used back
then:
http://doc.akka.io/docs/akka/2.4.12/AkkaJava.pdf
HTH,
Guido.
On Monday, October 31, 2016 at 10:27:18 PM UTC, Alireza Mohamadi wrote:
>
> Hi. As I mentioned, consider me as a newbie who is only good at coding.
> I want to write a project which I believe will have many simultaneous HTTP
> requests and many simultaneous DB queries being executed.
> I decided to choose Akka vs Quasar at last, and want to ask about how to
> fit my scenario in order to enjoy Akka miracles.
> My scenario is, client sends a request, I refer to DB in order to read
> his/her data, and then I do some processes and send a response. That's all!
> But in a very parallel manner.
> So this scenario is severely blocking. You say, use futures and let your
> actor do something else. That's called transforming a synchronous model to
> an asynchronous one.
> OK, I use futures, but send my actor to do what? Exactly what can I do in
> this case? Also let us assume I can suggest other jobs for this actor, how
> can I enjoy multiple threads running on a multi-core CPU? I have an actor
> which is cleaning the house until the pizza delivery arrives. So I hire
> another actor to help her, but what do I suggest to second actor? Feeding
> the cat? What if I don't have a cat?
> I mean that, in blocking (synchronous) model (Quasar uses, you know) it is
> simple. If you block an actor, we create another to do the same job but in
> parallel. They can both work on different tasks, but can easily get
> blocked. I don't want this model because I have chosen Akka, and I want to
> learn how can I transform that model efficiently to a non-blocking one so I
> can enjoy efficient parallelism.
> Thanks
>
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
