sneal

You make a good point about health checks. Its easy to conflate single node health with overall service health. The LB check should really be about "can this node serve HTTP traffic", even if the non-health check requests can only send back 5xx responses because their dependencies are failing.

I've also had the opposite problem where the health check would answer 200 OK, but the real app itself had a corrupted internal state because of a poor design/threading bug. If the health check had been the home page the node would have been pulled from the LB. While a more in-depth health check would have helped here, I think its better to alert/monitor/kill any node with a higher than normal error rate and leave the health check simple.

I think you meant the T34, the second most produced tank in history.

BOSH being different I think is why a former collegue of mine created a Chef cookbook for Concourse: https://github.com/dvanbuskirk/concourse

If you're only using an IoC container for wiring up some singletons that the main app knows about... I suppose he has a point. For most applications that I work on that would never fly, I rely heavily on the lifetime/scoping abilities of my DI framework (Autofac).