Creating a serverless web app with Airtable, Glitch, Node.js, & Ember.js
Ben Orozco

Very interesting; thank you!

However I definitely wouldn’t call this “serverless”. What I see is several backend components each handling a specific chunk of the workload (4–5 servers).

I get that this is a proof of concept for maximizing freemium here and there, but it’s important to note that this comes with several failure points making monitoring and debugging more complex and an increased technological risk because you now depend on several services, each with their own terms of services, each with incentive to try and rake in a few bucks at some point.

my 2¢

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.