[GitHub] [trafficcontrol] rob05c commented on issue #2198: Add Generic Traffic Ops Config Endpoint

[GitBox <gi...@apache.org>]

rob05c commented on issue #2198:
URL: https://github.com/apache/trafficcontrol/issues/2198#issuecomment-852254322


   I'll also note, this is less of an issue than it used to be. Especially with the transition from DeliveryService-Servers to Topologies.
   
   When I made this Issue, I don't think I or anyone realized literally 99% of the data for both cache config and the CRConfig was DeliveryServiceServers, which is a mathematical Outer Product. With DSS gone, "far more data than it needs" isn't very much, and scalability of TO and network traffic both really aren't issues, even for very large CDNs.
   
   With getting rid of DSS solving the technical issues, there's a lot of advantage in keeping using the standard API endpoints. Cache config (both Grove and ATS) doesn't require a custom endpoint, doesn't require changing TO to support new things or new features, other than those features' own native data.
   
   If we make a "Cache Config Endpoint," I strongly suspect it'll be a constant race, every time we need a new feature in t3c that needs existing data it didn't need before, calling the native Endpoint because t3c is safer, quicker, and more canary-able to deploy than TO, then adding that data to the "Cache Config Endpoint," then changing t3c to use that if it exists and the old if it doesn't, then finally removing the native API call when it's 2 major versions back and all TO versions supported by t3c have the new data. Or we can avoid all that, by just using the native real-data API.
   
   There are advantages to the "Cache Config Endpoint." But with the technical issues resolved by getting rid of DSS, I think there are a lot of advantages to continuing to use the native API. We should weigh the pros and cons of each.


-- 
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:
users@infra.apache.org