titiler VS terracotta

There's a lot to like about GDAL+Rasterio, although I've found having all HTTP requests go through GDAL's C API does result in some limitations on concurrency and multithreading. GDAL's configuration being based entirely on env vars also has its downsides: https://github.com/developmentseed/titiler/issues/186

TiMVT and TiFeatures, along with TiTiler for raster services, complete a trio of python-FastAPI services. The current roadmap includes merging TiFeatures & TiMVT, the vector-based services, into a single project to reduce code redundancy.

COGs are great, but from my experience micro services like titiler don't support complex styling logic. Is there a possibility to create a serverless WMS service with complex styling requirements?

Consider something like titiler if you want to serve the pile of geotiffs out to the web.

We were able to host 10gb six band rasters as well as 2cm RGB split into 100m tiles on S3 using COGS, mosaic.json and the TiTiler project which is powered by AWS lambda functions

One can also do raster calculus between two or more COGs with Terracotta: https://github.com/DHI-GRAS/terracotta/issues/221

I am currently working on setting up a web app using leaflet that can display .tif images along with some polygons and add some filters in the web app to better interact with the data. In the process of implementing this, I came to know that I need to use a tile server because I have large amounts of data and the tile server can help to serve the tiles on the web app. Based on my research, I guess these two are the main tools as of now: 1. Geoserver and 2. Terracotta. I am confused between the two. Can anyone suggest which one would be better for my use case and the pros and cons of both if possible? In case there's a different one that's better than the two mentioned above, it would be great if you can share the tool and your experience. Would be helpful.

Terracotta: Serverless GeoTiff Tile Server\ (12 comments)