plpgsql_check
geomesa
Our great sponsors
| plpgsql_check | geomesa | |
|---|---|---|
| 3 | 3 | |
| 605 | 1,388 | |
| - | 1.6% | |
| 8.2 | 8.9 | |
| about 1 month ago | 8 days ago | |
| C | Scala | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
plpgsql_check
-
Supabase Local Dev: migrations, branching, and observability
Finally, while you wait for us to make progress on the Language Server, we’ve added support for linting through the excellent plpgsql_check extension.
- Postgres Invalid objects
- PostGIS – Spatial and Geographic Objects for PostgreSQL
geomesa
- GeoMesa
-
Cool Dockerization Ideas
you could help dockerizing geomesa with/on Cassandra https://www.geomesa.org/ Currently its only dockerized with accumulo
-
PostGIS – Spatial and Geographic Objects for PostgreSQL
If you really need to scale beyond what Postgres/PostGIS can handle, then you might want to check out GeoMesa[1], which is (very loosely) "PostGIS for HBase, Cassandra, or Google BigTable".
That being said, you may not need it, because Postgres/PostGIS can scale vertically to handle larger datasets than most people realize. I recommend loading your intended data (or your best simulation of it) into a Postgres instance running on one of the extremely large VMs available on your cloud provider, and running a load test with a distribution of the queries you'd expect. Assuming the deliberately over-provisioned instance is able to handle the queries, you can then run some experiments to "right-size" the instance to find the right balance of compute, memory, SSD, etc. If it can handle the queries but not at the QPS you need, then read replicas may also be a good solution.
[1] https://github.com/locationtech/geomesa
What are some alternatives?
pgsentinel - postgresql extension providing Active session history
docker-postgis - Docker image for PostGIS
pg_show_plans - Show query plans of all currently running SQL statements
geometry-api-java - The Esri Geometry API for Java enables developers to write custom applications for analysis of spatial data. This API is used in the Esri GIS Tools for Hadoop and other 3rd-party data processing solutions.
orafce - The "orafce" project implements in Postgres some of the functions from the Oracle database that are missing (or behaving differently).Those functions were verified on Oracle 10g, and the module is useful for production work.
open-data - Free football data from StatsBomb
stud - Cartography 2019
tds_fdw - A PostgreSQL foreign data wrapper to connect to TDS databases (Sybase and Microsoft SQL Server)
sample-data - Metrica Sports sample tracking and event data
pg_plan_guarantee - Postgres Query Optimizer Extension that guarantees your desired plan will not change
pgaudit - PostgreSQL Audit Extension