System Architecture

I regularly spend time with business and technical leadership at large enterprise organizations where I walk through my big picture strategy around the API Lifecycle and governance. 90% of these conversations end with heads nodding, and folks saying, “That all sounds perfect, but where do we start?”. This is a question I am increasingly prepared to respond to, but truly understanding where someone is in their API journey, and providing them with some possible next steps for them to focus on, takes a lot of work. I just wrote about the four main areas needed to ground API strategy conversations, but I need to do more thinking about how to better help people in the moment, meeting them where they are, catering to what they need, speaking to their incentives, while also hanging guidance on an overall strategy that we can check-in on from time to time.

Documentation and guides from the team at Fly.io.

Respect for React, with receipts

I am working my way through 100+ Breaking Changes podcast conversations I have had , as well as 75+ customer conversations I have had this year, and reflecting on a book I just finished called The API-First Transformation (Coming Soon). Across these conversations I see four dimensions that are holding back enterprise organizations from achieving their desirable levels of conversations. While there are many points of friction across API operations, these four areas cause the most amount of instability and friction for teams in my experience.

When most people talk about Web3 or cryptocurrencies and related technologies, they usually mean blockchains. But blockchain is only the first generation of distributed ledger technology (DLT). As with any new technology, once people see how it works, new generations come along rapidly to address the faults in the previous ones.  On this sponsored episode…

The industry is impatient for disaggregated and shared memory for a lot of reasons, and many system architects don’t want to wait until PCI-Express 6.0 or

When applications talk to applications, how do we prove the credibility of service-to-service connections? Enter SPIFFE and SPIRE.

Who is responsible for the current state of affairs? For the world as it is? — a capitalist dystopia offering nothing.

Public key crypto for everyone, publicly auditable proofs of identity.

Generated by create next app

Combine your drives and clouds into one database that you can organize and explore from any device. Designed for creators, hoarders and the painfully disorganized.

A post-modern modal text editor.

Once these capabilities have been established, Ops teams can begin to look further afield and explore leveraging the value of their data through activities like testing and optimization.

Have you ever found yourself in a situation where you need to deploy a quick Git repository on a machine within your LAN? Here's what to do.

The pros and cons of asynchronous programming through the lens of how it plays out in the very high steaks FinTech world.

Improve correctness using Semgrep's AST-based autofix

What is causing the delay in the software development? What are the ways to speed up software development process? Follow our 7 essential tips!

"Discuss docs, "in place"

We're experimenting with an API for making persistent storage eviction under heavy memory pressure more predictable, and we'd love your feedback.

In the past I was part of a project with rather specialized data. It was important to create records in a database that had a certain validity, but it was al...

The thing I love most about programming over the years has always been design and optimization work....

A certain amount of traffic tips the scales to make serverless a more expensive bill at the end of the month

We assume that browser caches are near-instantaneous, but data shows that retrieving an object from cache can take hundreds of milliseconds!

I know little about GraphQL, but based on what I’ve seen so far, it is a very promising technology for providing access to data and delivering over open APIs. Unlike other API specifications whose focus is on services, GraphQL is data centric and essentially provides a standard way to query datasets and deliver schema documentation in machine actionable formats. So I’m very hyped about this but need to understand the current state of affairs and how far this can go.

HTTP is a stateless protocol, meaning each request is independent of any other request. This is different from a stateful protocol, where ...