It's strange that this person didn't also describe the lessons they'd learned about Content Marketing, but I guess it doesn't work if you point that out.
* Serverless typically implies something accessible from more than the host you're on
* It's not zero configuration, there's at least 1 configurable parameter (albeit with a sensible default)
* I'm actually not even clear why this is a document store limited to JSON, other than you're piping it though a JSON python module.
Having done some things like this in the past, as you continue, you'll probably want to create subdirectories based on the first N characters of the UUID, but I'm not sure you wouldn't get considerably more value of just putting your json blobs into an AWS Dynamo table.
Thanks for posting this, I found the format incredibly helpful, and it kind of makes me want to produce a run-rate estimator in a similar format. I often wind up overspending on side-project ideas for failing to take into account the costs of services I'll wind up using.
Judging by the Stripe fees, I'd hazard that your cumulative revenue is in the $30k range. I'm sure there are marketing and advertising expenses that aren't listed here, but that seems like a pretty healthy gross margin.
This seems like a use-case that a whole lot of people are excited about since microservices are presently in vogue. What would make me want to choose Apollo over, say, Dropwizard (http://dropwizard.io) if we assume that I'm not a developer at Spotify?
Then perhaps it's inappropriate to claim that "Otto can deploy to many different infrastructure providers" until "Otto can deploy to many different infrastructure providers".
The short form is that in a Stacked Ranking performance measurement system, you rank every employee in an ordered list. Most often the next thing you hear is that the top X% of employees are the ones who will be given raises/bonuses, and the bottom Y% of employees are the ones who will be finding new jobs.