Best practices for serving contours to end users

[AVLGISADMIN]

Hi, I'm curious how everyone is serving contours to your end users, if you aren't pointing people to a public rest service at the state level or something similar.

Vector Tiles? Cached map service? Straight feature service?

I'm looking at publishing vector tiles because the area I'm in has a lot of elevation changes so contours at anything below a 10-20ft interval are so dense that performance is terrible for a regular feature service.

Are vector tiles the way to go or should I be looking at something else? Thanks.

[BillFox]

are you working with a "chess-board" of DEM GeoTiff files in a mosaic dataset?

[AVLGISADMIN]

No I'm working with a dense contour feature class. They are 1ft contours which is what my end users are asking for but given the mountainous region we are in its a lot of data and vertices. I was thinking of using generalize to reduce the number of vertices, but I'm not sure if I can do that and stay within tolerance for 1ft contours, maybe I can go up to 2ft.

If you have any workflow advice I'd be happy to hear it, I tried creating a vector tile set to upload to agol but it seemed like it didnt work correctly, it would only draw in certain sections of the contours.