Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's how I use the two together.</p> <p>Think of it like this...</p> <p>Object-Oriented Programming introduced new layers of encapsulation. At the object level (with private members). OSGi just enables JAR-level encapsulation. Without OSGi, as soon as its compiled, it all melts into one pot. OSGi enforces the interface at the JAR level. And because of that, you have cleaner modularity and better code (for the same reasons any type of encapsulation is good).</p> <p>I only use OSGi to do the JAR-level encapsulation. Any features that overlap such as scaling up certain modules based on usage, I do in Akka, because the API is higher-level and so easier to do and maintain.</p> <p>But, many things about them don't overlap, so you should be able to see what goes where pretty easily with that rule of thumb in mind.</p> <p>OSGi is to me just very useful for enforcing a good design, because it has rules for how I can consume a service... enforcing an interface at the JAR-level.</p> <p>I'd say your last paragraph explains it well. Just modularize it like you would for any large-scale software. But now they are OSGi bundles instead.</p> <p>If you have follow-up questions, please do comment. I can edit to say more. I've been using the two together for a while now.</p> <p>Edit: Response to comments</p> <p>Reading your question, it seems you may know some things I don't. Which I can't be sure of, so let me know if this post misses its mark. I'm an Akka guy who later did some OSGi, if you did that the other way around, you may be aware of options that I am not.</p> <p>sharing the actor system is trivial. OSGi bundles don't cause inversion of control like a framework. You just call it like any other library code.</p> <p>Wherever you are creating the actor uses system.actorOf calling the class of an actor in another bundle, and that's it. Your question seems to imply you know more about other OSGi options or perhaps are thinking that OSGi will do inversion of control and so each bundle would be stuck with its own actor system.</p> <p>If it's still unclear, I'd recommend a quick prototype. Just pass the first end-to-end test that uses the design and then refactor adding in OSGi.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can OSGi and Akka benefit from each other? How is this structured?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDante Romero
    1. USDante Romero
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can OSGi and Akka benefit from each other? How is this structured?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you for your explanation. Is the cooperation between OSGi and Akka common? Is my solution in the last paragraph a common way to structure this, and are their sometimes other structures used?
      singulars
      1. PO
      1. USArthur C
    2. COI'm not sure if it's common. But, it wouldn't surprise me if it's done but not heard of because both are very common tools... and for the most part, they are orthogonal to each other. So it's not really a combo that would come up in conversation. The way use use OSGi with Akka is the same as you would for any code. I haven't run into any cases where what I need to do with Akka is different than if it were regular synchronous code. So, the recommendations you find in a good book on OSGi, such as OSGi in action, should work. And same for Akka. They are mostly orthogonal to each other.
      singulars
      1. PO
      1. USDante Romero
    3. COIt would be useful to have an example (maybe on github if it is too complex for SO) of how the ActorSystem can be shared between multiple bundles. I envision certain bundles providing services via the ActorSystem and other bundles being able to reference them (via the same instance of the ActorSystem) to send messages to the Actors defined in other bundles.
      singulars
      1. PO
      1. USaxiopisty
 

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