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.
Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
j
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
quer
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
N
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 a
