consolidate to a single raster tiling service and domain name

[hrodmn]

We are on a mission to consolidate the MAAP project down to a single raster tiling service. Until recently, there were three services running:

• titiler.maap-project.org: an outdated titiler application with /cog endpoints and support for registering and using custom MosaicJSON via the /mosaics endpoints.
• titiler-stac.maap-project.org: a titiler application with the /stac endpoints for rendering tiles from STAC item hrefs
• titiler-pgstac.maap-project.org: a titiler.pgstac application with support for rendering tiles from STAC collections in the MAAP STAC API via the /collections endpoints or /searches endpoints

For reasons we want to move everything to a single service. The plan has been to build the titiler.pgstac service up to include the /cog, /stac, and /mosaics endpoints so that any MAAP user could run their existing workflows on that service instead ofone of the other two. Over the last several months we have accomplished the goal of upgrading the titiler.pgstac service to include all of the features from the other services.

• Update eoapi-cdk with custom titiler-pgstac runtime #26
• Add mosaicjson endpoints #31
• add /stac routers to titiler-pgstac.maap-project.org #27

titiler-stac.maap-project.org has been torn down already!

The last step is to move users over to the titiler.pgstac service via one of these approaches:

• request that users update their applications and notebooks that point at titiler.maap-project.org to use titiler-pgstac.maap-project.org, then eventually shut down titiler.maap-project.org and the associated Lambda.
• flip a switch to redirect traffic to titiler.maap-project.org to the titiler.pgstac application instead of the old titiler application, then shut down the titiler application.

The situation is slightly complicated by the fact that both the titiler and titiler.pgstac applications are running the SMCE AWS account with custom domains registered in the UAH AWS account.
We may want to migrate this infrastructure over to the MCP AWS account in the near future so we need to consider that possibility when we commit to a plan.

Option 1: Tell users to update code to use titiler-pgstac.maap-project.org instead of titiler.maap-project.org

advantages:

• no more infrastructure changes besides tearing down the old titiler application and the titiler.maap-project.org domain infrastructure
• we could accomplish it in phases by adding warnings to the old endpoint responses and eventually returning an error that tells users to redirect traffic to titiler-pgstac.maap-project.org
• could even overlay warning text to any tiles requested from the old application

disadvantages:

• existing code that uses titiler.maap-project.org would need to be updated
• working with users is more difficult than making infrastructure changes
• the default action by users will be no change, which will eventually result in an error
• titiler-pgstac... is an awfully long url to recall and type every time you make a dynamic plot in a notebook

implications for transfering to MCP

• ...

Option 2: Direct traffic to titiler.maap-project.org to the titiler.pgstac application instead of the old titiler application

advantages:

• As long as all of the endpoints from the titiler application are supported by the titiler-pgstac application, users should not notice a difference
• If the above is true, users will require minimal or no notification of the changes
• The shorter domain name is better!

disadvantages:

• There may be some minor parameter name changes that would break existing formatted URLs for the titiler application endpoints
  • e.g. coord-crs -> coord_crs and things like that

implications for transfering to MCP

• ...

@jjfrench @wildintellect please feel free to add other options or make any edits that you want, and can you help me fill in the details about what these options mean for the potential move to an MCP account?

[wildintellect]

Worst/Best idea, shorten it to tiles.maap-project.org or tiler.maap-project.org ...

I don't think the MCP move will cause an major disruptions, as you can just repoint the DNS once the service is ready over in MCP. There's just a lot of work to do an MCP deployment and migrate the pgstac database to MCP.

[hrodmn]

Worst/Best idea, shorten it to tiles.maap-project.org or tiler.maap-project.org ...

We could also follow the eoAPI example and use raster.maap-project.org

A totally new url would be the most work but if there is a moment to reconsider the domain name now is probably the best time.

[jjfrench]

We could keep both existing domain names and add raster.maap-project.org, that could give us a period of time to transition people to raster.maap-project.org gradually? (most like option 2)