I think it would be very usuful to have a DuckDB datasource for both (vector) tile service and features service, this would allow a lot of flexibility in terms of supported formats and queries, since DuckDB with the spatial extension is able to read most of the GDAL sources.
For the tile service, there's unfortunately no st_toMVTGeom function in DuckDB now, but it's possible to read the convert the output geometry (usually wkb) to a MVT tile using geozero.
I think it would be very usuful to have a DuckDB datasource for both (vector) tile service and features service, this would allow a lot of flexibility in terms of supported formats and queries, since DuckDB with the spatial extension is able to read most of the GDAL sources.
For the tile service, there's unfortunately no
st_toMVTGeomfunction in DuckDB now, but it's possible to read the convert the output geometry (usually wkb) to a MVT tile usinggeozero.