Hi all,
I'm looking to have an in-memory database in GeoServer which can handle a few million SimpleFeatures with great spatial indexing and some secondary indices on other non-spatial columns. To that end, I have two quick questions:
1. Which in-memory GeoTools datastores have folked used and liked?
I've found Spatialite and some H2 options in the docs:
http://docs.geoserver.org/latest/en/user/community/spatialite/index.html
http://docs.geoserver.org/latest/en/user/data/database/h2.html
https://github.com/orbisgis/h2gis-gs
Are there others? And how well do they perform?
2. Does anyone have any particular libraries to suggest for building such a DataStore/FeatureSource from scratch?
Thanks in advance,
Jim
Jim,
Is this just for sake of performance? If so, have you considered PostGIS with the proper memory allocations and config parameters for your use case?
This was an interesting thread on the topic: http://dba.stackexchange.com/questions/2041/postgresql-force-data-into-memory
···
On Tue, Aug 16, 2016 at 9:29 AM, Jim Hughes <jnh5y@anonymised.com> wrote:
Hi all,
I’m looking to have an in-memory database in GeoServer which can handle
a few million SimpleFeatures with great spatial indexing and some
secondary indices on other non-spatial columns. To that end, I have two
quick questions:
- Which in-memory GeoTools datastores have folked used and liked?
I’ve found Spatialite and some H2 options in the docs:
http://docs.geoserver.org/latest/en/user/community/spatialite/index.html
http://docs.geoserver.org/latest/en/user/data/database/h2.html
https://github.com/orbisgis/h2gis-gs
Are there others? And how well do they perform?
- Does anyone have any particular libraries to suggest for building
such a DataStore/FeatureSource from scratch?
Thanks in advance,
Jim
Geoserver-users mailing list
Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
Hi Jason,
Yes, this is definitely with performance in mind. Another piece of the puzzle is the data can be updating quite frequently. Our current solution is to hold all of this data in memory in a GeoTools datastore (1) backed by Kafka. We are hitting some limits as folks run complex queries. We think that they could be better served by a more full-featured in-memory database.
Additionally, and sadly, I don’t have much option to deploy PostGIS:(.
Cheers,
Jim
- http://www.geomesa.org/documentation/user/kafka_datastore.html
···
On 08/16/2016 09:43 AM, Jason Newmoyer wrote:
Jim,
Is this just for sake of performance? If so, have you considered PostGIS with the proper memory allocations and config parameters for your use case?
This was an interesting thread on the topic: http://dba.stackexchange.com/questions/2041/postgresql-force-data-into-memory
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
On Tue, Aug 16, 2016 at 9:29 AM, Jim Hughes <jnh5y@anonymised.com> wrote:
Hi all,
I’m looking to have an in-memory database in GeoServer which can handle
a few million SimpleFeatures with great spatial indexing and some
secondary indices on other non-spatial columns. To that end, I have two
quick questions:
- Which in-memory GeoTools datastores have folked used and liked?
I’ve found Spatialite and some H2 options in the docs:
http://docs.geoserver.org/latest/en/user/community/spatialite/index.html
http://docs.geoserver.org/latest/en/user/data/database/h2.html
https://github.com/orbisgis/h2gis-gs
Are there others? And how well do they perform?
- Does anyone have any particular libraries to suggest for building
such a DataStore/FeatureSource from scratch?
Thanks in advance,
Jim
Geoserver-users mailing list
Geoserver-users@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
I see, bummer on PostGIS not being an option. Although depending on how large the dataset is and how frequent the updates, that could become a problem with Postgres. Or really any relational DB backed datastore, including SQLite or H2.
···
On Tue, Aug 16, 2016 at 1:39 PM, Jim Hughes <jnh5y@anonymised.com> wrote:
Hi Jason,
Yes, this is definitely with performance in mind. Another piece of the puzzle is the data can be updating quite frequently. Our current solution is to hold all of this data in memory in a GeoTools datastore (1) backed by Kafka. We are hitting some limits as folks run complex queries. We think that they could be better served by a more full-featured in-memory database.
Additionally, and sadly, I don’t have much option to deploy PostGIS:(.
Cheers,
Jim
- http://www.geomesa.org/documentation/user/kafka_datastore.html
On 08/16/2016 09:43 AM, Jason Newmoyer wrote:
Jim,
Is this just for sake of performance? If so, have you considered PostGIS with the proper memory allocations and config parameters for your use case?
This was an interesting thread on the topic: http://dba.stackexchange.com/questions/2041/postgresql-force-data-into-memory
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com
On Tue, Aug 16, 2016 at 9:29 AM, Jim Hughes <jnh5y@anonymised.com> wrote:
Hi all,
I’m looking to have an in-memory database in GeoServer which can handle
a few million SimpleFeatures with great spatial indexing and some
secondary indices on other non-spatial columns. To that end, I have two
quick questions:
- Which in-memory GeoTools datastores have folked used and liked?
I’ve found Spatialite and some H2 options in the docs:
http://docs.geoserver.org/latest/en/user/community/spatialite/index.html
http://docs.geoserver.org/latest/en/user/data/database/h2.html
https://github.com/orbisgis/h2gis-gs
Are there others? And how well do they perform?
- Does anyone have any particular libraries to suggest for building
such a DataStore/FeatureSource from scratch?
Thanks in advance,
Jim
Geoserver-users mailing list
Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users