Basically those plans represent the size of the clusters that are deployed for your APIs.

All of them come with a minimum 3 node database layer, and each plan increases the node counts. The medium and large plans also increase the CPU/mem of the database nodes.

Thanks! It's a great point to make. Early on I worked on a "migration" ability for the resources, so that every change you make automatically updates the underlying database. But the longer I worked on that, the more I realized I could create/delete as many APIs as I wanted working out what's necessary. Then scale it up for longevity. And the time it took to create/delete APIs was nearly as fast as some of the build times I've experienced for front-end applications.

That's ultimately what I think the value is: API development as hyper-iterative as front-end apps.

I'm still clearly working out how to describe this value. I'm developing more examples to help define what I think the best use-cases are.

There is a lot going on in the tech industry, and this is the question you should be asking yourself right now.

Be careful how you approach things you feel have simple answers.

Charity Majors, Kelsey Hightower, Tim Jarratt, Tim Banks, and Brian LeRoux - Profiles in software for Attainable Newsletter.

The art of resiliency includes letting go, but that is not to be confused with losing.

Permanence and certainty are not always something you have, rather it’s what you work to achieve.

Kelsey’s favorite place on earth is earth, and it reflects his sense of team and community.

Charity's philosophy on coaching should not be judged by its appearance.

Don't forget to look at industries where maybe there already exists large solutions or organizations, but aren't doing as much as can be done to help those that need it most. Education and Healthcare are a few of these. You might not make billions of dollars improving Kindergarten classes in North America, but you could "change" the world.