Mapserver VS Liquibase

If you want to get into web GeoDjango is a popular option for the backend, but you could also learn to roll your own with flask/FastAPI. You also have some choice of JavaScript libraries for the frontend, [Leaflet]() and [OpenLayers]() are likely the most popular frameworks, but there are others (personally I'd recommend OpenLayers as it's the only one backed by OSGeo as far as I know). It also wouldn't hurt to... Source: over 1 year ago

GeoServer and MapServer both have full OGC services, WMS, WMTS, WFS, etc. They have caching and tiling. Accessing OGC services through a web server will require an OGC server. Source: over 2 years ago

Welcome here, fellow MapServer user! 🗺️. Source: over 2 years ago

As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago

Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago