News for hackers. Stuff that matters.

A comment on Thoughts on Uber’s List of Postgres Limitations. Parent comment

Re:Thoughts on Uber’s List of Postgres Limitations by majewsky on Wednesday August 03, 2016 @08:23AM (#12217384)
> static page cache behind cdn

I wouldn't want my page behind a CDN. CDNs make users much more trackable across sites.

My point isn't that CDNs are bad for everyone. My point is, once more, that most questions are not as simple as they may appear.

[ Parent | on HN ]
Re:Thoughts on Uber’s List of Postgres Limitations by paulddraper on Wednesday August 03, 2016 @10:42AM (#12218232)
> CDNs make users much more trackable across sites.

How does has CDN do this in a way that a "regular" web deployment wouldn't?

[ Parent | on HN ]
Re:Thoughts on Uber’s List of Postgres Limitations by MustardTiger on Wednesday August 03, 2016 @11:01AM (#12218396)
The same CDN is serving thousands of sites, so they can track a ton of what users do. CDNs are perfectly placed to capture and sell user stats.
[ Parent | on HN ]
Re:Thoughts on Uber’s List of Postgres Limitations by j_s on Wednesday August 03, 2016 @10:53AM (#12218324)
A third party (CDN provider) can easily track visits entirely server-side across all of the sites that it serves. Typically this is sites owned by lots of different companies users could otherwise visit without any of those companies knowing of visits to any other companies' sites -- the CDN knows.

This also comes up when the CDN handles SSL termination.

[ Parent | on HN ]