rob05c commented on issue #4534: Fix ORT atstccfg to allow using new features in the latest Traffic Ops URL: https://github.com/apache/trafficcontrol/pull/4534#issuecomment-603398314 >If we upgrade TO first like we usually do TC has always supported running any component with any other component one version back, ORT breaking that was a regression, and IMO we should continue to support that. TC components should be loosely-coupled. There are innumerable disadvantages to tightly-coupled components. In fact, at our organization, we didn't used to have a strict order, and IMO we should never have adopted that deployment procedure. Requiring a strict upgrade order makes TC brittle and dangerous. It's much safer, robust, and resilient to require all components to support one version back of all the other components they talk to, so they can be upgraded or rolled back in any order. Sometimes there are operational reasons one component needs updated first, and mandating an order makes that impossible. In the event a component unexpectedly needs to be rolled back, supporting one version back also allows that to be done quickly and safely. Without it, it would mean every component after it the "deployment order" has to be rolled back in sequence. Making an already tricky situation much more dangerous. It also tightly couples our development, and makes it more difficult to develop each individual component. It means one person or team can't develop on one product, and implement a feature one component at a time with a clean interface. They have to be aware of all the ramifications of all the other components and their deployment order.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
