Zappa VS turf

If people aren't familiar, there's a similar project for Python that's fantastic: https://github.com/zappa/Zappa

Chalice was a consequence, a reaction from AWS to the release of (Zappa Framework)[https://github.com/zappa/Zappa] that provide a very good alternative to migrate very quickly a Django/Flask or any WSGI compliant solution in Python.

Use Zappa https://github.com/zappa/Zappa and host as a Lambda, simple setup and deployment, Lambda only costs when processing requests, no servers to mess around with

One of my favorite options that is probably the most cost-effective is to deploy using a 'severless' model on AWS Lambda using zappa which supports deploying Python webapps to AWS in this way. Zappa also makes it super easy to deploy in just a couple commands! The README includes instructions for everything you might need, including handling sensitive information like your database passwords, running django management commands, setting up DNS, etc.

Deployment works nicely with Docker. I often use AWS AppRunner because it's really easy and just scales. Some people use AWS Lambda with Zappa but I don't recommend it unless you really want to spend less than $15 a month. You will probably need Django Storages to save uploads to an S3 bucket. At some stage you might want to put a CloudFront distribution in front of everything but the configuration of the caching behaviour might be a bit confusing when you do it the first time.

It doesn't have to be an either-or! I have several apps in production that were developed on Django or Flask, and deployed to Lambda using Zappa.

If you need a relational DB, you can use AWS Aurora or RDS and use cloud functions ('lambda' in AWS) that you can invoke with HTTP to process the document first. Zappa will do a lot of the configuration for you if you go that route.

Lambda + API gateway, this library bundles a Django application into a lambda https://github.com/zappa/Zappa . 1 million free invokes from aws, scale to zero, plugs into your RDS

I use Zappa, it just schedules a frequent execution of the lambda: https://github.com/zappa/Zappa#keeping-the-server-warm

to measure distances and convert between our parameters I'm using TurfJS, for which binding is even more trivial:

Turf.js is an open-source geospatial analysis library that can process various location data, such as the center of gravity and distance calculations.

Isochrones are manually calculated using turf.js assuming 1.2m/s walking speed after the subway trip. These are simple buffers around each station/prior isochrone and do not take the street network into account.

Not to take away from you learning, which I think is awesome, I was wondering if you know about http://turfjs.org/ which provides a lot of simple modules … and is surprisingly hard to find. Their `distance` modules may be relevant in this case.

you can use client side libraries like Turfjs to do buffers https://github.com/Turfjs/turf/tree/master/packages/turf-buffer

Tools: custom Javascript (with heavy use of turf.js) for data processing and creating the 3D model, Blender, 3D printing, lost wax casting

I've integrated https://turfjs.org/ with mapbox before and it was pretty fun

References Amazon Location Service Turf.js MapLibre GL JS Leaflet OpenLayers Cesium Mapbox GL JS