Deployment

Deployment

BigGeo Search seamlessly integrates into your existing architecture stack as a containerized service, effortlessly connecting with your database and hosting infrastructure. In this documentation, we'll focus on outlining three primary deployment methods for BigGeo's headless container: Azure, Snowflake, and self-hosted (on-premises/local) setups. However, it's worth noting that additional deployment options may exist beyond these three, which can be explored based on specific requirements and preferences.

Azure

BigGeo Search is distributed through Azures Marketplace here. This listing allows you to quickly deploy a BigGeo Container into your current Azure ecosystem.

Specific Azure deployment instructions can be found here.

Snowflake

BigGeo Search is distributed as a Snowpark Container Service in Snowflake. This deployment allows you to get the most out of your geospatial data all within the governance of Snowflake's ecosystem.

Specific Snowflake deployment instructions can be found here.

Self-Hosted (Hosted/On-Premises/Local)

BigGeo's headless nature as an independent container service offers the flexibility to host it wherever you prefer. Whether you choose on-premises deployment, local development environments for your developers, or other architectural setups not previously mentioned, BigGeo can seamlessly adapt to your needs.

For more specific self-hosted instructions, check out the self-hosted guide here.

NOTE:

If using BigGeo with a NestJS server then gRPC Client will not send fields that contain underscore _ in their names unless the keepCase options is set to true in the proto loader configuration.

Please refer to the documentation here.