Designing APIs for humans: Object IDs - DEV Community
dev.to · 3,916 words · saved by 1 readers
Choosing your ID type Regardless of what type of business you run, you very likely require...
Choosing your ID type Regardless of what type of business you run, you very likely require a database to store important data like customer information or status of orders. Storing is just one part of it though; you also need a way to swiftly retrieve the data – which is where IDs come in. Also known as a primary key, IDs are what you use to uniquely specify a row in a table. When designing your table, you want a system where your IDs are easy to generate, unique and human readable. The most simplistic approach you might take to IDs when using a relational database is to use the row ID, which
related reading
- Everything I know about good API designseangoedecke.com
- How to (and how not to) design REST APIs · stickfigure/blog Wiki · GitHubgithub.com
- Why We Don’t Trust the Database With Authentication – Sturdy Statisticsblog.sturdystatistics.com
- sbensu: Breaking changes in JSON APIsblog.sbensu.com
- The Problem with Using a UUID Primary Key in MySQL — PlanetScaleplanetscale.com
- Mediumjkebertz.medium.com
- Understanding IndexedDB. The complete guide.blog.xnim.me
- Stripe Dot Devstripe.dev
- APIs All the Way Down - Not Boring by Packy McCormicknotboring.co
- Stytch - A better way to build authstytch.com
- OpenAI Platformplatform.openai.com
- Using Snowflakes for database IDs | Matteo Contrinimatteosonoio.it