I did something similar in an S3 uploader POC - https://github.com/smoketurner/uploader
It runs an embedded Netty managed by Dropwizard for the actual ingestion part and then maintains the Jetty endpoints for the admin endpoints and other random endpoints. -Justin On Thursday, December 15, 2016 at 11:12:39 AM UTC-5, Chris Berry wrote: > > HI, > > We are using Dropwizard as our microservice framework, and have a lot > invested in it. Both for all of our many “devops” needs and with many > custom Bundles (Kafka streams, etc). > > I would love to do the following and am unsure how to proceed. I’m hoping > the kind experts herein might give me some guidance. > > I would like to add an _additional_ HTTP server to Dropwizard. Such that; > * The existing, built-in Jetty server can still supply all of our > canned devops needs (i.e. HealthChecks, AdminServlet, MetricsServlet, …) > So that I don’t have to reinvent the wheel. > * And a _second_ server will supply my API. In particular, I’d like to > use Netty, or perhaps Akka-http for this. > > What is the best way to go about this?? > Use a ManagedObject?? > > Any advice would be greatly appreciated. Google hasn’t turned up much… > > Thanks much, > -- Chris Berry > > -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
