title: Running multiple Quarkus instances on one machine
body: <p>I have an application separated in various OSGI bundles which run on a single Apache Karaf instance. However, I want to migrate to a microservice framework because</p>
  <ul>
  <li>Apache Karaf is pretty tough to set up due its dependency mechanism and</li>
  <li>I want to be able to bring the application later to the cloud (AWS, GCloud, whatever)</li>
  </ul>
  <p>I did some research, had a look at various frameworks and concluded that Quarkus might be the right choice due to its container-based approach, the performance and possible cloud integration opportunities.</p>
  <p>Now, I am struggeling at one point and I didn't find a solution so far, but maybe I also might have a misunderstanding here: my plan is to migrate almost every OSGI bundle of my application into a separate microservice. In that way, I would be able to scale horizontally only the services for which this is necessary and I could also update/deploy them separately without having to restart the whole application. Thus, I assume that every service needs to run in a separate Quarkus instance. However, Quarkus does not not seem to support this out of the box?!? Instead I would need to create a separate configuration for each Quarkus instance.</p>
  <p>Is this really the way to go? How can the services discover each other? And is there a way that a service A can communicate with a service B not only via REST calls but also use objects of classes and methods of service B incorporating a dependency to service B for service A?</p>
  <p>Thanks a lot for any ideas on this!</p>