Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Dropwizard-Specific code in to dropwizard Module #41

Closed
Sage-Pierce opened this issue Jan 28, 2020 · 0 comments
Closed

Move Dropwizard-Specific code in to dropwizard Module #41

Sage-Pierce opened this issue Jan 28, 2020 · 0 comments

Comments

@Sage-Pierce
Copy link
Contributor

Describe the feature

There is currently some Dropwizard-specific code for Metrics that depends on Codahale that would likely be cleaner in a Dropwizard-specific Module.

In addition, we should be able to move some Dropwizard Bundle code that we've found useful with Expedia that wires Stanzas in to the Server LifeCycle

Rational

Since Rhapsody is a streaming framework for web services, it makes sense to have minimal resources that play nice with common web frameworks, like Dropwizard (and, Spring, etc.)

Example Scenario

If I'm using a Dropwizard application, it would be nice to pull in a Rhapsody Dropwizard module and immediately have an idea of the classes I might want to use

Sage-Pierce pushed a commit to Sage-Pierce/rhapsody that referenced this issue Jan 28, 2020
Sage-Pierce pushed a commit to Sage-Pierce/rhapsody that referenced this issue Jan 28, 2020
Sage-Pierce pushed a commit to Sage-Pierce/rhapsody that referenced this issue Jan 30, 2020
Sage-Pierce pushed a commit to Sage-Pierce/rhapsody that referenced this issue Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant