4 ms·
Are you saying you should configure the server to local time to save you one less configuration on the presentation layer? That doesn't make sense to me. I real
by JohnMakin 3y ago
Are you saying you should configure the server to local time to save you one less configuration on the presentation layer? That doesn't make sense to me. I really can't think of any benefits to setting the server to local time that doesn't offset the huge load of negatives.
Here's something you may not be thinking about - your presentation layer may save a configuration step, but now every system that interacts with your server (who have all likely defaulted to UTC) have to know about this now. Think - logging infrastructure, schedulers, cloud infra, etc. So now you have to configure all those as well. Anything that touches the host will need to be reconfigured to save one very minor and commonly done thing on the presentation layer. Really doesn't make sense, as an infra guy.
- lxgr 3y ago> every system that interacts with your server (who have all likely defaulted to UTC) have to know about this now. No, why? Almost all APIs/interfaces use zoned timestamps or seconds since the Unix epoch. The argument of “servers must run in UTC” sounds a bit like “servers must run with an English locale” to me in that sense, as if the locale changed the name of API parameters or enum values instead of just human-readable strings.