System Architecture

More trees than forest

Using the power of trees, we can quickly decipher a message sent in the world-famous Morse code.

It is very rare for any of the major semiconductor suppliers of the world to ever admit that things are going wrong, even when we all know that they have

How a multicloud and offline approach can prepare your organization to be the one customers go to when your competitors are scrambling.

Wix rewrote its checkout API and had to migrate it in a way with no downtime and with as few incidents as possible. Rather than going through a cycle migration, the company's engineers did a linear migration, which provided a seamless user experience.

Why the Ruby philosophy is the exact opposite of other programming languages?

At the end of our earlier article on John Ousterhout's talk at Netdev 0x16, he had concluded that TCP was unsuitable for data-center environments for a variety of reasons. He also argued that there was no way to repair TCP so that it could serve the needs of data-center networking. In order for software to be able to use the full potential of today's networking hardware, TCP needs to be replaced with a protocol that is different in almost every way, he said. The second half of the talk covered the Homa transport protocol that he and others at Stanford have been working on as a possible replacement for TCP in the data center.

A community verified user validator for Mastodon

Dropbox has to render a lot of thumbnails when we browse a folder containing a bunch of images. Here's how they serve them efficiently at scale. Simple approach Thumbnail is created for each image present in a Dropbox folder and uploaded to a blob store like s3 or hdfs. Each thumbnail thus has a path using which it can be fetched on the client and shown to the end user.

An overview of infrastructure architecture and implementations with Pulumi.

A system and method for instrumenting program instructions. A processing system includes a compiler and a profiler. The profiler is configured to instrument an application by inserting one or more instrumentation instructions in the application. During execution of the application, execution is monitored and a particular condition is detected. Responsive to the condition, a portion of the code which corresponds to the detected condition is identified. A request is conveyed for recompilation of code which corresponds to code. Prior to recompilation of the code, the profiler instruments the portion of code. Execution and monitoring of the execution continue, and instrumentation/recompilation may be repeated. Initially, relatively little of the application code may be instrumented. As execution and monitoring continues, more and more of the application code may be dynamically instrumented during execution.

The ActivityPub protocol is a decentralized social networking protocol based upon the [ActivityStreams] 2.0 data format. It provides a client to server API for creating, updating and deleting content, as well as a federated server to server API for delivering notifications and content.

The cosmo CLI is your one-stop-shop for all things Cosmonic. It puts at your fingertips the ability to interact with and manage your account, preferences, your constellations, and more. As we progress through the developer preview phase, more and more functionality will be added to cosmo.

WebAssembly (WASM) is a binary instruction format for a stack-based virtual machine. In familiar terms, WASM is used as a compilation target for various programming languages (C, C++, Rust, or Golang, for example), generating a compact binary with a known format. Mozilla Developer Network describes WebAssembly as having huge implications for the web platform — it provides a way to run code written in multiple languages on the web at near native speed, with client apps running on the web that previously couldn’t have done so.

Learn how to bring React’s paradigm of Composability to the world of APIs, microservices, and databases — powered by Wundergraph…

The Federated Credential Management API is shipping in Chrome 108.

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.