Hi everyone,
I’m currently working on a small web project and I’m splitting my workflow between the backend and frontend since I’ll need a “heavy” processing component for automated spatial operations.
This part mainly involves running scripts that perform spatial tasks such as calculating point distances, handling geometry intersections, and updating labels based on spatial results.
Apart from that, the project also includes the usual web elements — a standard database, content pages, multimedia, etc.
So far, I’ve been considering Strapi for the backend and Vercel for the frontend, but I suspect I’ll need an additional service to handle the spatial processing layer.
Has anyone here worked on something similar (ideally keeping costs low)?
What tools, architectures, or workflows would you recommend?
Any feedback or corrections to this general approach are more than welcome.
Thanks in advance for any advice or experiences you can share! 😊
Top comments (3)
Hey! While I have not worked on something similar I know a few Strapi users who have leverages plugins for similar use cases i.e market.strapi.io/plugins/@gismark-... or market.strapi.io/plugins/strapi-le...
Hey Victor, that is really interesting and useful, appreciate it!
It really depends on how much data you’re processing and how complex the spatial operations get.
For light or moderate workloads, your setup can stay simple:
If some of the work is lightweight (like simple distances, buffers, or intersections on small datasets), you can even run it client-side with Turf.js — it’s perfect for quick spatial logic without extra infra.
For heavier or long-running tasks, you can introduce a job queue later (e.g., Redis + worker) so your processing runs smoothly without blocking the main app.