dhinus

3 ms·

1. 1.▲
   Enable your Devs to do Ops: Runbooks in the DevOps era(blog.buildo.io)

   8 points by dhinus 9y ago|0 comments
2. 2.▲
   Blockchain Transport(ljn.io)

   3 points by dhinus 9y ago|0 comments
3. 3.▲
   by dhinus 9y ago

   For ease of deployment and to solve the problem of "what version of service_b is compatible with version x of service_a"? IMHO this makes sense if the microservices are developed by the same team. If we're talking about servi
4. 4.▲
   by dhinus 9y ago

   Because we want to make sure that in the Docker registry we have _all_ services tagged with the latest commit. For example you might have a Git history like this: * 89abcde Fix bug in service_b * 1234567 Initial commit including service_a a
5. 5.▲
   by dhinus 9y ago

   Depends on many factors... It can vary from 5 to 30 minutes, from the moment someone presses "merge" on a pull request and the moment that change is live on a test environment. The average is probably around 10-15 minutes. The bui
6. 6.▲
   by dhinus 9y ago

   Our apps are made by 5-15 (micro)services. I'm not sure if this approach would scale to hundreds of services managed by different teams. We store the source code for all services in subfolders of the same monorepo (one repo <-> o
7. 7.▲
   The three laws of config dynamics(blog.buildo.io)

   6 points by dhinus 9y ago|0 comments