I’m so excited that this book is back on track!

Build APIs You Wont Hate 2: This Time Its Serious

Roughly 80% of the internet is roughly built APIs, held together with enough duct-tape to choke all the hamsters powering it. Let's learn how to build them properly.

#apidesign
#apidevelopment

https://leanpub.com/build-apis-you-wont-hate-2

Node.js and Serverless Architecture: Building Future-Ready Cloud Applications in 2025

https://zekond.com/read-blog/136083_node-js-and-serverless-architecture-building-future-ready-cloud-applications-in.html

Explore how Node.js and serverless architecture can help you build scalable, cost-efficient, and future-ready cloud applications in 2025. Leverage the power of serverless computing for optimal performance.

#NodeJS
#Serverless
#CloudComputing
#WebDevelopment
#ScalableApps
#AWSLambda
#FutureOfTech
#BackendDevelopment
#JavaScript
#TechTrends2025
#APIDevelopment
#DevOps

Top Node.js Development Best Practices for 2025 | Tuvoc Tech

https://heyjinni.com/read-blog/202079_top-node-js-development-best-practices-for-2025-tuvoc-tech.html

Discover the top Node.js development best practices for 2025 to improve performance, security, and scalability. Stay updated with the latest coding standards and optimization techniques.

#NodeJS
#WebDevelopment
#JavaScript
#BackendDevelopment
#CodingBestPractices
#TechTrends2025
#APIDevelopment
#FullStackDevelopment
#SoftwareEngineering
#PerformanceOptimization
#ScalableApps
#SecureCoding
#NodeJSTips

"While each component — API design, QA, and DE — plays a crucial role, their collective impact is far greater when seamlessly integrated. Siloed processes lead to fragmented experiences, but unified workflows foster consistency and drive better outcomes.

Organizations that bridge the gaps between API development, testing, and digital experience monitoring are better positioned to deliver products that not only function but delight users. By focusing on alignment across these domains, businesses create scalable, resilient digital ecosystems that adapt to evolving customer needs.

I’ve seen this borne out by the highest-performing technical teams I’ve worked with over the years. The best teams inevitably have support from the top-down, executives and management who are tech-savvy and truly serious about making their organization a market leader. Without that kind of influential internal support, software teams are often squeezed and forced to try to do more with less, which is almost always a recipe for poor customer experience."

https://nordicapis.com/the-road-to-customer-loyalty-starts-at-the-api-layer/

Ready to build a RESTful API with PHP? Dive into our comprehensive guide and learn the essential steps to create secure, efficient APIs for your web projects. Perfect for developers looking to expand their backend skills!

Visit for More: https://orbitwebtech.com/create-a-restful-api-with-php/

This was an absolute beast to write, a complete guide to OpenAPI v3.1!

Use this guide instead of the Swagger.io guide which was stuck on OpenAPI v3.0, and instead of trying to wrap your brain around the specification which isn’t intended to be user documentation.

#OpenAPI #APIDevelopment
#apidesign #APIDocumentation
https://docs.bump.sh/guides/openapi/specification/v3.1/introduction/what-is-openapi/

Learn how to close down and wind up an API without making a mess of it all in this post by me. Avoid surprising your customers with these simple communication and monitoring methods. #APIDevelopment #WebAPI https://blog.treblle.com/best-practices-deprecating-api/

Great visualisation for the efficiency of cursor based pagination from @jessicamauerhan at #ipc #webinale. Did you know that limit-offset pagination has to scan the whole database to figure out what comes next?

That's a long time if you're on the last page of thousands of results. But it doesn't have to be that way - investigate adding cursors to your data sets. With appropriate indices, the time required is constant.

API Podcast Alert!

Learn all about Redocly the handy OpenAPI documentation tool with a Swiss army CLI that does everything (even linting!), and a bit more about the plan for OpenAPI v4 (a.k.a Moonwalk).

Good natter in general with @lornajane who I always love catching up with.

#APIDesign
#APIDevelopment #apidocumentation

https://apisyouwonthate.com/podcast/redocly-openapi-moonwalk-lorna-jane-mitchell/

Check out my interview with @darrel_miller and @vincentbiret from Microsoft's Graph API team

Learn all about Kiota - a bloody good SDK generator, find out how the Microsoft Graph API works (it’s absolutely massive) and find out what’s coming in OpenAPI v4.0 )code named Moonwalk). @OpenApiSpec #APIDesign #APIDevelopment #DevRel https://apisyouwonthate.com/podcast/microsoft-kiota-graph-api-darrel-miller-vincent-biret/

There’s an amazing plethora of apps that make using this platform amazing, and I am happy to have paid for quite a few.

I wonder if the next major frontier is interfacing with donations to the supporting the server and mastodons development. I have several friends who thought paying a subscription to an app meant they were also supporting their instance and masto API development… I hope app developers make that a reality someday!

If you work with APIs and haven’t dug into OpenAPI yet, here’s a full blown introduction to get you started from absolutely zero context. Written by me, for the excellent folks at @httptoolkit.

https://httptoolkit.com/blog/introduction-to-openapi/

I’ve been writing a bit about API Versioning lately.

1. Explaining why I think API versioning is usually a bad idea that forces extra work onto consumers by lazy developers, and how to avoid needing to do it.

https://blog.treblle.com/my-version-api-versioning-better-than-most-versiong-being-done/

2. If you are going to do it, please don’t mess around with semantic versioning because it’s pointless.

https://apisyouwonthate.com/blog/versioning-apis-semantically/

Discuss!

Deprecating a package with 200,000 installs a week feels funny, but I've been waiting for a chance to bin off swagger-cli for ages. It's not being maintained (some upstream dependencies are which helps) but even the name is out of date. Thankfully the #Redocly CLI does everything it did, but better, so I recommend you go use that.

More deprecations of old #OpenAPI tooling to come as I find more viable modern alternatives.

#APIDesign #APIDevelopment #OpenSource
https://www.npmjs.com/package/@redocly/cli

Woah, I'm reviewing #Redocly CLI and I just noticed the amazing split command!

$ redocly split api/openapi.yaml --outDir output/

This will neatly split a sprawling messy #OpenAPI description into multiple documents using $ref, reducing duplication, making it easier to work with.

Get it: https://github.com/Redocly/redocly-cli/