Caching and reformatting about tileserver

[nvkelso]

Hi @ambientlight, thanks for checking out Tilezen and tileserver :) Generally speaking yes tileserver like you see it is used in prod, but off the latest tagged release v1.4.0, which is very close to master but master has a few more dev commits in it today since the release 20 days ago.

We pre-cache many tiles for Mapzen's production setup, and actually use tilequeue to most of that initial generation. Tileserver remains on the hot path in production, though, for requests where the tile is not yet in cache.

The behavior with reformat_from_stored_json sounds weird here in tileserver. @rmarianski can you comment on that, please?

[ambientlight]

@nvkelso Thanks! So you mean you are serving cached tiles statically on something like CloudFront-backed s3 buckets? And then if there are no such static tiles available -> you would then route it to tileserver to compute? This would that explain the difference in behavior.

[nvkelso]

Yes. We write out to S3 and then have Fastly at the edge. If Fastly doesn’t see the tile on S3, it routes the request to tileserver.

…

On Wed, Apr 12, 2017 at 9:48 PM, Taras Vozniuk ***@***.***> wrote: @nvkelso <https://github.com/nvkelso> Thanks! So you mean you are serving cached tiles statically like on something like CloudFront-backed s3 buckets? And then if there are no such static tiles available -> you would then route it to tileserver to compute? This would that explain it I guess. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA0EO-XM8Uoja10LKxH8PgQXQXq0zZtlks5rvakrgaJpZM4M8N1k> .

[ambientlight]

Got it, thanks a lot!

[rmarianski]

The behavior with reformat_from_stored_json sounds weird here in tileserver. @rmarianski can you comment on that, please?

Logic that's no longer relevant. Should get cleaned up.

[rmarianski]

This just got cleaned up in master in #94.