Muses

Upstream Uptime #3: Making Local-Runnable Services The Norm

This entry is in the series Upstream Uptime

I recently wrote about upstream-centric architectures and how we have to alter our making when we adopt them. A key alteration: change the definition of "deploy" to include "local-runnable". In that long list of problems I encountered in a real upstream-centric app I worked with a few years ago, a great many of the first-round

Upstream Uptime #3: Making Local-Runnable Services The Norm Read More »

Upstream Uptime #2: The Problem In Practice

This entry is in the series Upstream Uptime

We started talking about the new upstream-centric style or architecture the other day. I wanted that to be a first swing at describing the problem, but I didn’t really get there. Let’s do that now. The problems I see in many orgs attempting this approach, service-orientation or microservices, etc., are most visible when we come

Upstream Uptime #2: The Problem In Practice Read More »

Upstream Uptime #1: Grasping the Problem

This entry is in the series Upstream Uptime

Increasingly, we build apps by composition with other apps. Granting that this approach is viable, still it comes with a cluster of related problems, and to really win with this style, we’ll have to address them. An "upstream" is an independent program that my application’s correct behavior depends on at runtime. It is typically 1)

Upstream Uptime #1: Grasping the Problem Read More »

One Story, One Day

TDD Pro-Tip: The step-wise technique has to account for what the user experiences when, so I have to build ways to control that when stories get bigger than a day. (A new friend asked the question: when stories get hefty, how do we "live at HEAD" without exposing our users to code that’s still WIP.)

One Story, One Day Read More »

Scroll to Top