Intedspence.combyTed SpenceAPI Design: Friendly ID numbersExploring the usability issues around records and their identitiesMar 13, 20231Mar 13, 20231
Intedspence.combyTed SpencePart 2: Developing a data layer for your DotNet APIThe foundation of a successful API is a robust CI/CD pipeline for schema changesFeb 13, 2023Feb 13, 2023
Intedspence.combyTed SpenceAPI design: The problems with PUT and PATCHCan we solve the usability problems of the humble update API?Feb 20, 2023Feb 20, 2023
InCodeXbyTed SpenceAPI Design: The art of writing error messagesIf you don’t talk to your developers about proper error message design, who will?Mar 12, 2023Mar 12, 2023
Intedspence.combyTed SpencePart 1: Designing an API with DotNet and PostgresFor your next project, why not try one of the best open source database servers?Jan 30, 20231Jan 30, 20231
Intedspence.combyTed SpenceLayered security for DotNet Core APIsA helpful security technique for defense in depth using middlewareNov 23, 2022Nov 23, 2022
InCodeXbyTed SpenceThe best accessories for your APIA collection of little features and tips that will matter for your API serviceNov 13, 2022Nov 13, 2022
Intedspence.combyTed SpenceAn API Should Debug ItselfTips and techniques for establishing solid quality assurance goalsAug 27, 2018Aug 27, 2018
Intedspence.combyTed SpenceCase Study: Gap Analysis for a Unified APIUsing tools from business school to tackle a big projectSep 17, 2018Sep 17, 2018
Intedspence.combyTed SpenceAPI Defense in DepthProtect your API from internal mistakes as well as external hacksOct 15, 2018Oct 15, 2018
Intedspence.combyTed SpenceDesigning a Great API: Error MessagesThe technology behind an API must increase its usability, not its complexityOct 23, 2018Oct 23, 2018
Intedspence.combyTed SpenceDesigning a Great API: Consistency and ConveyanceA goal for user experience designers is critical for developer experienceOct 24, 2018Oct 24, 2018
Intedspence.combyTed SpenceAPI Design: Backwards CompatibilityA discussion of all the ways an API can cause problems for its usersNov 1, 20181Nov 1, 20181
Intedspence.combyTed SpenceProtecting APIs with layered securityThe first in a series of articles on API design issues for SaaS projectsApr 12, 2021Apr 12, 2021
InCodeXbyTed SpenceShould you allow internal-only APIs?The second in a series of articles on API design for SaaS projectsApr 20, 2021Apr 20, 2021
Intedspence.combyTed SpenceAvoid these API Performance pitfallsPart three in a series on API design: Common mistakes that affect response timeApr 26, 2021Apr 26, 2021
InCodeXbyTed SpenceShould APIs use 404 as an error code?The humble 404 error, so familiar on the web, is a problem for an APISep 24, 202111Sep 24, 202111
Intedspence.combyTed SpenceCaching strategies for authenticationYou should expect high performance authentication from your APIsMar 11, 20223Mar 11, 20223
InCodeXbyTed SpenceHow should your API handle data dependencies?When two fields in a data structure are linked, usability can be trickyOct 3, 2022Oct 3, 2022
Intedspence.combyTed SpenceThirteen API caching mistakes to avoidSo many ways to mess up your API with poorly designed cachesJul 11, 2022Jul 11, 2022