Databases
StackOverflow2013
Postsdbo
POAkka or Reactor
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAkka or Reactor
    primarykey
    data
    text
    <p>I am in the process of starting a new project (java-based). I need to build it as a modular, distributed and resilient architecture.</p> <p>Therefore I would like to have the business processes to communicate among themselves, be interoperable, but also independent.</p> <p>I am looking right now at two frameworks that, besides their difference in age, express 2 different views:</p> <ul> <li>Akka (<a href="http://akka.io" rel="noreferrer">http://akka.io</a>)</li> <li>Reactor (<a href="https://github.com/reactor/reactor" rel="noreferrer">https://github.com/reactor/reactor</a>)</li> </ul> <p>What I should consider when choosing one of the above frameworks?</p> <p>As far as I understand till now, Akka is still somehow coupled (in a way that I have to 'choose' the actor I want to send the messages to), but very resilient. While Reactor is loose (as is based on event posting).</p> <p>Can someone help me understand how make a proper decision?</p> <p><strong>UPDATE</strong></p> <p>After reviewing better the <a href="http://doc.akka.io/docs/akka/snapshot/java/event-bus.html" rel="noreferrer">Event Bus</a> of Akka, I believe in some way the <a href="https://github.com/reactor/reactor#events-selectors-and-consumers" rel="noreferrer">features expressed by Reactor</a> are already included in Akka.</p> <p>For example the subscription and event publishing, documented on <a href="https://github.com/reactor/reactor#events-selectors-and-consumers" rel="noreferrer">https://github.com/reactor/reactor#events-selectors-and-consumers</a>, can be expressed in Akka as following:</p> <pre><code>final ActorSystem system = ActorSystem.create("system"); final ActorRef actor = system.actorOf(new Props( new UntypedActorFactory() { @Override public Actor create() throws Exception { return new UntypedActor() { final LoggingAdapter log = Logging.getLogger( getContext().system(), this); @Override public void onReceive(Object message) throws Exception { if (message instanceof String) log.info("Received String message: {}", message); else unhandled(message); } }; } }), "actor"); system.eventStream().subscribe(actor, String.class); system.eventStream().publish("testing 1 2 3"); </code></pre> <p>Therefore it seems to me now that the major differences between the two are:</p> <ul> <li>Akka, more mature, bound to Typesafe</li> <li>Reactor, early stage, bound to Spring</li> </ul> <p>Is my interpretation correct? But <strong>what is conceptually the difference between the Actor in Akka and the Consumer in Reactor</strong>?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSimeon Leyzerzon
    1. USDavid Riccitelli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAkka or Reactor
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAkka or Reactor
      1. This table or related slice is empty.
      1. VTModeratorReview
    3. VO
      singulars
      1. POAkka or Reactor
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAkka is not bound to be used by Scala, in fact, a majority use it from Java.
      singulars
      1. POAkka or Reactor
      1. USViktor Klang
    2. COHello Viktor, yes, I'm using Akka with Java as well. What I meant is that Akka is part of the Typesafe ecosystem, whereas Reactor to Spring. When developing in Scala though, Akka would probably be the most appropriated choice.
      singulars
      1. POAkka or Reactor
      1. USDavid Riccitelli
    3. COViktor, I believe we could say that Akka implements the Reactor pattern (with the Event Bus, Dispatchers and Mailboxes), am I correct?
      singulars
      1. POAkka or Reactor
      1. USDavid Riccitelli
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload