News for hackers. Stuff that matters.
Re:Aviator: locally launch a service and all its dependent s... by rgarcia on Wednesday April 08, 2015 @03:31PM (#9343281)
The problem of keeping this kind of configuration up-to-date is an interesting one. I'm curious if anyone has tried encoding the local development configuration in how they run integration tests so that it never falls out of date.
Re:Aviator: locally launch a service and all its dependent s... by maerF0x0 on Wednesday April 08, 2015 @03:21PM (#9343173)
> $ npm run-script dev-server

> Starting Website

> [ERROR]

I'd start with crushing the soul of whomever didnt put in quality logging (debug package). Next I'd cry about my lack of debugger knowledge for nodejs.

Re:Aviator: locally launch a service and all its dependent s... by dnstevenson on Wednesday April 08, 2015 @08:38PM (#9345117)
Re:Aviator: locally launch a service and all its dependent s... by schimmy_changa on Wednesday April 08, 2015 @03:10PM (#9343100)
I wonder how Netflix addresses this- looking at their Hystrix page they have tons and tons of microservices...
Re:Aviator: locally launch a service and all its dependent s... by schimmy_changa on Wednesday April 08, 2015 @03:11PM (#9343104)
(page is https://github.com/Netflix/Hystrix/wiki) <-- this is not the way they handle it, just has a good image showing how crazy the number of microservices they handle is
Re:Aviator: locally launch a service and all its dependent s... by ridgepablo on Wednesday April 08, 2015 @09:59PM (#9345415)
This seems like a useful tool for managing a complex service configuration problem. Nice work.