So if you're going to be putting them in a db, why did you 'port' them to airtable? Wouldn't it be cheaper to store the files on s3 and insert in the db when you get your schema and everything solidified?
sorry I didn't mean "port" literally, I meant it as a slang term. I meant "move everything over".
Airtable uses s3 to manage the file upload assets (I think). I like using Airtable over a traditional RDBMS since its extremely user friendly and easy to update your db schema. I don't have to memorize anything on the backend (E.g. with MS-SQL, it was always in an uphill battle working with sql-server management studio, figuring out what settings I need to tweaked, etc). Airtable's GUI is super intuitive if your familiar with excel / MS-access. It took me a few days to learn and figure out airtable, MS-Access took me about 3 months+.
This and your other comments read like ads. I don't mean to say that you're not being genuine, but when I (and presumably others) read a thread like this and see overly-enthusiastic reviews it raises a degree of skepticism. I wouldn't like to criticise you, especially since you just seem to be trying to inform others about a product you're pleased with, but i think there's a general problem on hn with comments above a certain threshold of complimentariness. Some are obvious shills, but there's a big grey area where it's harder to tell.
