GeePaw

UDispatch #1: Start With a Bulk Reverse Proxy

Change, Coaching /
This entry is part [part not set] of 5 in the series UDispatch

UDispatch has multiple layers of functionality in it. The first thing it is: a reverse proxy on the dev box that knows your upstreams and knows they’re sets. When you’re coding in a downstream, you typically have multiple upstreams you’re developing against. Service#1, Service#2, and so on. Your code sends HTTP to those services, they […]

UDispatch #1: Start With a Bulk Reverse Proxy Read More »

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

Change, Coaching /
This entry is part [part not set] of 4 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

Change, Coaching /
This entry is part [part not set] of 4 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

Coaching, Change /
This entry is part [part not set] of 4 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 »

Story-Splitting #3: Easy Customer First

Change, Coaching /
This entry is part [part not set] of 3 in the series Story-Splitting

A valuable trick I sometimes forget: first solve the easy customer. Before we continue, I feel we need to pull some real cases in this set of muses about story splitting. It can’t be super-concrete, because a) confidentiality and b) too much detail hides the idea. Hopefully, this will help a little with figuring out

Story-Splitting #3: Easy Customer First Read More »

Story-Splitting #2: Choosing Which Criterion To Relax

Change, Coaching /
This entry is part [part not set] of 3 in the series Story-Splitting

I use my sorted list of story criteria when I have to back off getting the perfect story. We went into this yesterday here, and for the threading impaired, the blog will be up late tomorrow. There are a bunch of criteria for the perfect story, so many that at times I’m at a loss

Story-Splitting #2: Choosing Which Criterion To Relax Read More »

Story-Splitting #1: Understanding the Criteria

Change, Coaching /
This entry is part [part not set] of 3 in the series Story-Splitting

I sort my criteria for a story, so that when I step back from "perfect story", I step in the right direction. A "perfect" story has several attributes. Each of them contributes to its value in different ways, but maybe before we even list them we have to talk a little about what that value

Story-Splitting #1: Understanding the Criteria Read More »

Scroll to Top