|
|
|
The idea and approach we would like to use with NOMAD development follow a bit what has been shown to be successful for other Big Data/cloud enterprises.
|
|
|
|
We do not want to copy exactly the technologies, but some of them and the basic ideas behind them.
|
|
|
|
|
|
|
|
For this the following talk is instructive:
|
|
|
|
[Fast Delivery](https://www.youtube.com/watch?v=icvtIK83I_g) talk by Adrian Cockcroft (38 min)
|
|
|
|
|
|
|
|
Some basic ideas are also [in this older article](http://highscalability.com/blog/2011/12/12/netflix-developing-deploying-and-supporting-software-accordi.html)
|
|
|
|
|
|
|
|
Also [Adrian Cockcroft Blog](http://perfcap.blogspot.de/) is quite interesting.
|
|
|
|
|
|
|
|
The idea is to let the developer free to experiment (freedom and responsibility), by making it simple to change and redeploy part or even the whole infrastructure and make it possible to have multiple version coexisting and talking to each other.
|
|
|
|
|
|
|
|
Trying to have micro-services can help having well defined and small units of development.
|
|
|
|
|
|
|
|
All that is automatizable should be automatized, in particular testing and integration testing.
|
|
|
|
Create artificial failures to see how the system can cope with failures ([Simian Army](http://devops.com/2014/03/27/netflix-the-simian-army-and-the-culture-of-freedom-and-responsibility/))
|
|
|
|
|
|
|
|
From our side we plan to use [Docker](https://www.docker.com/)
|
|
|
|
|