←back to thread

OpenStreetMap's New Vector Tiles

(tech.marksblogg.com)
479 points marklit | 1 comments | | HN request time: 0s | source
Show context
kibwen ◴[] No.42183410[source]
Does this reduce the operating costs of hosting OSM-based maps, since presumably they require less CPU spent on rendering and vectors consume less storage/bandwidth?
replies(4): >>42183467 #>>42183661 #>>42184016 #>>42184618 #
hamiltont ◴[] No.42183661[source]
Yes and No.

No because the official OSM tile layer is heavily subsidized by Fastly (€720k last I checked) and rendering by AWS (€40k)

Yes because technically it would use fewer resources thus easier on AWS+Fastly and also easier to self-host

In last risk assessment I read closely(1) OSM noted "If we lost [Fastly] sponsorship, we would likely cut off all third-party access to the standard tile layer and run a small number of Varnish servers."

As I understand it, primary drivers for vectors was not cost more improving internationalization, generally enabling client-side rendering decisions, and driving a modern toolchain that would net multiple follow-on benefits

I'm a bit behind, there is more recent info available at (2)

1.https://operations.osmfoundation.org/2024/01/25/owg_budget.o... 2. https://osmfoundation.org/wiki/Finances

replies(2): >>42185506 #>>42186002 #
treyd ◴[] No.42185506[source]
I wonder if it would be feasible to distribute tile data in a DHT. There is a single source of truth that could seed the DHT and users would share the load of serving the data. It'd have to be opt-in on individual nav devices for privacy and battery reasons, but anyone running their own OSM proxy would have an incentive participate.
replies(1): >>42188707 #
1. gloflo ◴[] No.42188707[source]
Way too much latency I am sure.