Skip to content

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.


Follow @CodeOpinion

HTTP API

HTMX: What’s Old is New Again

What’s old is new again, kind of. HTMX fits into that motto for me and it’s getting pretty popular, but at the same time It gets a lot of pushback. I’m going to take a step back and explain how we got to where we are in current web dev, which will explain what HTMX is. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. How did we get here? So first, quickly, what is HTMX? If you’re unfamiliar with it, HTMX gives you access to AJAX,… Read More »HTMX: What’s Old is New Again

Build better HTTP APIs

Many of the business systems we build are for managing life cycles and workflows. It provides ways to make the state transition from beginning to end. One of the challenges when building systems is that they evolve, and you can start leaking business logic to the frontend or clients where you end up with duplicate logic littered all over the place. Here’s a way to solve that issue so you can build better HTTP APIs. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. State Machine For… Read More »Build better HTTP APIs

How to (and how not to) design REST APIs

Everyone seems to love best practices or rules for designing REST APIs. But is all this guidance good advice? Let’s find out. YouTube Check out my YouTube channel, where I post all kinds of content accompanying my posts, including this video showing everything in this post. “REST” API Rules I stumbled upon a post outlining rules around how you design REST APIs. These posts are often found on LinkedIn, and I usually shake my head when reading them, so I figured I’d review this one and give some feedback. I shake my head because some of these will seem pretty standard, but… Read More »How to (and how not to) design REST APIs