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

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

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


   Personally, I really like the method that TR uses, which is similar to what this "Generic Traffic Ops Config Endpoint" would be. With few exceptions, TR gets all of its config from a single endpoint which is basically unversioned (so we don't really have to jump through Semantic Versioning Hoops), and if we wanted to, it would be very easy to cache the CRConfig in TO and simply check a timestamp in the DB to know if it has changed with each request. This would offload a tremendous amount of DB load if we were to do this for caches as well, since they make up the vast majority of TO API requests (via `t3c`). An endpoint like this would also lend itself nicely to server snapshots.
   
   But, like you said, if we were to eliminate DSS in favor of topology-based assignments, that would also alleviate a lot of the DB load.


-- 
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