Table des matières
Dynamic Distributed Service Locator
On ne trouve rien sur Google à propos de ce “Dynamic Distributed Service Locator”, c'est un projet tout neuf sans RFC globale.
Where does DDSL help ?
In many big companies you have a lot of services (SOAP, REST, etc) spread across many servers on several different Web Containers/Application Servers/ESB (Weblogic, Glassfish, Tomcat, Jetty, Mule, etc). At least this is the situation where I work. You also have several different environments: test, preprod, prod etc with different servers and databases etc.
One service might use several other services.
You might also have (or want) several different versions of one service to run at the same time.
All those service locations… This means a lot of configuring.
This is where DDSL helps..
What is DDSL ?
DDSL - Dynamic Distributed Service Locator
No admin needed.
You don't have to manually add your service / version to the repository.
Your application can automatically register its location. – It can also register it's “quality” (Clients will preferred locations with better “quality”.
Locations on “localhost” will be preferred.
You can mix several “environments” (prod, test) within the same DDSL-repository.
Automatically load balancing between multiple locations with same “quality”.
Service is automatically removed from repository, if it crashes/go down.
DDSL has no single point of failure.
It uses ZooKeeper as its dynamic distributed storage.
A repository of services (with version) and their current locations
More info can be found here.
Module DDSL pour le Play! framework: https://github.com/mbknor/ddsl-playframework-module