Set-up services basis #27
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Disabled listener and runner projects, as they are not compatible with DropWizard 0.7.0* - Upgraded to DropWizard 0.7.0-rc2 - Upgraded to Gradle 1.11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea of Pipeline has always been to exist of small (micro)services with very specific purposes. To make that possible, some way of service discovery and global configuration management is required.
With this pull-request I want to set-up the basis for these (micro)services structure, this includes:
The idea is to do all communication between services over HTTP(s), as that is the simplest way of communicating we all know (we being the languages, tooling, ...). Also the most readable and firewall-friendly way to communicate.
For ideas and tools/libraries to use (possibly with some extension), I've been looking at the Netflix OSS tools/libraries. Based on those, I came to the following set-up:
Based on Eureka
Based on Archaius
Eureka is already HTTP-based, and Archaius is easily extended to be HTTP-based.