Hacker News new | past | comments | ask | show | jobs | submit login

You need to be able to troubleshoot things in production though.

Perhaps whenever a developer wants to troubleshoot the orchestrator could make a clone of the container. The clone continuously receives the same input as the original and gets to believe that it affects the back end in the same way. That way the developer can dissect the container without impacting real data.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: