Date: Tue, 31 Aug 2021 21:00:18 -0700
<p>Welcome to Remotely Interesting brought to you by <a href="https://www.netlify.com/?utm_source=remotelyInteresting&utm_medium=episodeSummary-tzm&utm_campaign=devex"><strong>Netlify</strong></a>.</p><p><strong>People who were remotely interesting:</strong></p><ul> <li><a href="https://twitter.com/cassidoo"><strong>Cassidy Williams</strong></a></li> <li><a href="https://twitter.com/jlengstorf"><strong>Jason Lengstorf</strong></a></li> <li><a href="https://twitter.com/philhawksworth"><strong>Phil Hawksworth</strong></a></li> <li><a href="https://twitter.com/Tzmanics"><strong>Tara Z. Manicsic</strong></a></li> </ul><p><strong>SHOW NOTES:</strong></p><p>Who's got a favorite database?</p><ul><li>Everyone</li></ul><p><strong>Structured vs. Unstructured Data</strong></p><ul> <li>our first database experiences (lots of MySQL)</li> <li>learning about databases</li> <li>Jason thinks his brain gets bigger when he learns things</li> <li>Microsoft Excel does everything</li> <li>MongoDB & mongoose the GraphQL</li> <li>It is SQL or SQL</li> <li> <a href="https://en.wikipedia.org/wiki/Shadow_and_Bone_(TV_series)">Shadow and Bone</a> (putting this here for Phil)</li> </ul><p><strong>How do you use DBs in a Jamstack architecture?</strong></p><ul> <li>having to do DBs for "real" sites</li> <li>abdicating responsibilities to the experts at a Database as a Service</li> <li>sharding and giggling</li> <li>from limited options & complicated setups to lots of new options<ul> <li><a href="https://fauna.com/">FaunaDB</a></li> <li><a href="https://hasura.io/">Hasura</a></li> <li><a href="https://supabase.io/">Supabase</a></li> <li> <a href="https://planetscale.com/">PlanetScale</a>, etc.</li> </ul> </li> <li>decoupling the frontend from the backend</li> <li>via API endpoints & serverless functions, we're standardizing communication</li> </ul><p><strong>DX & How we choose DBs</strong></p><ul> <li> <a href="https://graphql.org/">GraphQL</a> user interface (<a href="https://www.electronjs.org/apps/graphiql">GraphiQL</a>)</li> <li>on the basis of the API, writing queries, accelerating dev workflow</li> <li>how much do we need to know about the DBs</li> <li>Phil is wise, you're welcome, Phil</li> <li>the dev's comfort level</li> </ul><p><strong>Who needs the top-tier?</strong></p><ul> <li>you probs aren't going to hit Twitter-scale</li> <li>by the time you outgrow the service, you'll prob. have the money to go bigger</li> <li>dbs aren't that incredibly different</li> <li>ask the company what your next step should be if you hit a limit</li> <li>kicking tires/free tiers are so valuable</li> </ul><p><strong>What features do we look for?<br /></strong>- a clear, understandable API<br />- an easy onramp to getting started/getting data<br />- what am I building & what are the cost implications (rate limits, etc.)<br />- even really brilliant, smart people like Jason mess up, a story about loops<br />- having a playground like GraphiQL<br />- a discussion of GraphQL hesitancy<br />- Cassidy's professional conclusion, "ehhh"<br />- Jason talks about depends</p><p><strong>Cassidy exhibits her humor mastery and it shines like the sun! 🌤</strong></p><p>a resource! <a href="https://serverless.css-tricks.com/"><strong>https://serverless.css-tricks.com/</strong></a><strong><br /></strong>another resource: <a href="https://graphql.org/learn/">https://graphql.org/learn/</a> <br />a fantastic Phil Supabase resource: <a href="https://ntl.fyi/3BsJheT">https://ntl.fyi/3BsJheT</a></p><p><strong>TidBits & ThoughtThings™️<br /></strong>What is the worst form of storage you own?</p><p><br /></p><p>As always, we hope you find it remotely interesting.</p><p><br /><strong>TRANSCRIPT:</strong></p>
