Writing to cache/store after generation about tileserver HOT 4 CLOSED

I took out the store code in #85 because Mapzen is trying to optimize its tile response time (by doing more work in tilequeue and relying less on tileserver).

We probably should have kept it in there and configured it to be off on our servers. I'll look at doing that next week, but for now if you want to take a look at that pull request to see what was taken out you can see how we implemented storing tiles in tileserver.

from tileserver.

Like @iandees mentioned, We're planning on adding some kind of caching back in ourselves. Sounds like we might want to think about growing an abstraction for this, or maybe use the same store interface that exists but grow a redis implementation for it.

from tileserver.

@tomass In the meantime, I suggest using the tagged production release instead: https://github.com/tilezen/tileserver/releases/tag/v1.4.0.

from tileserver.

Thank you a lot for information and suggestions! It was really helpful!

from tileserver.