A passionate Full-Stack Software Engineer 🚀 motivated by a desire to tackle real-world challenges through technology and craft meaningful user experiences.
Totally agree — Redis is ridiculously fast for geospatial lookups, especially with GEOSEARCH. It's hard not to appreciate that speed when you're prototyping or need real-time responsiveness.
That said, I do feel the tension when thinking long-term. Redis geohashing is awesome for radius queries, but once you need more complex spatial relationships or accurate geometry handling, options like PostGIS really start to shine.
My take: if the use case requires fast nearby-object lookups (e.g. building a ride-hailing app), Redis is a solid choice. But if you're dealing with deeper spatial logic or long-term persistence (e.g. urban planning or GIS analysis), PostGIS is likely the better tool.
Curious to hear what others are doing!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
insane how quick redis can pull this off imo - you ever feel torn picking between geohashing in redis vs a full spatial db long-term?
Totally agree — Redis is ridiculously fast for geospatial lookups, especially with GEOSEARCH. It's hard not to appreciate that speed when you're prototyping or need real-time responsiveness.
That said, I do feel the tension when thinking long-term. Redis geohashing is awesome for radius queries, but once you need more complex spatial relationships or accurate geometry handling, options like PostGIS really start to shine.
My take: if the use case requires fast nearby-object lookups (e.g. building a ride-hailing app), Redis is a solid choice. But if you're dealing with deeper spatial logic or long-term persistence (e.g. urban planning or GIS analysis), PostGIS is likely the better tool.
Curious to hear what others are doing!