Databases
StackOverflow2013
Postsdbo
POComponent-based application with scalability in mind: OSGi or Akka?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POComponent-based application with scalability in mind: OSGi or Akka?
    primarykey
    data
    text
    <p>For my master thesis I'm developing an application framework for selling tickets for large events. My main requirements are modifiability, scalability and performance. My clients (event organisers) should be able to easily replace a component at runtime and add functionality. An example of such a component could be the seat assignment component.</p> <p>My mentors said to look at OSGi. The idea of loosely coupled bundles is certainly appealing. When looking for alternatives I discovered Akka. This framework promises a lot of things, like scalability and high performance. I wondered if Akka's concept of actors suits my modifiability requirements. Akka seems more productive than OSGi, so development would be faster. Akka also seems more fit for scalability. With OSGi I would have a harder time.</p> <p>If you have experience in both OSGi and Akka, which would you recommend for me? What are the pro and cons of both technologies when comparing them? And finally, are there are any good alternatives to OSGi or Akka that cover my requirements?</p> <p><strong>EDIT</strong></p> <p>First, thank you for the replies so far, you're a great help. As mentioned below, I'm trying to compare apples and pears. A more logical question would be: How can OSGi and Akka be used together and benefit from each other? How is this structured? Do all your actors reside in one OSGi bundle, do they each get a separate bundle, is there a hybrid solution or isn't there really a 'right' way to do it?</p> <p><strong>EDIT bis</strong></p> <p>I posted a follow up question <a href="https://stackoverflow.com/questions/20163507/how-can-osgi-and-akka-benefit-from-each-other-how-is-this-structured">here</a>, asking how to combine OSGi and Akka.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USArthur C
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI think you should open a new question for that.
      singulars
      1. POComponent-based application with scalability in mind: OSGi or Akka?
      1. USAndrei I
    2. COI will do that!
      singulars
      1. POComponent-based application with scalability in mind: OSGi or Akka?
      1. USArthur C
 

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