chapter two

2 The layer nobody designed

 

This chapter covers

  • Tracing how an improvised promotion layer gets built
  • Seeing why Git and CI can’t make promotion decisions
  • Understanding what the layer lacks as it scales
  • Recognizing what changes when promotion gets its own system

Chapter 1 provided a glimpse of Lumen Retail’s improvised promotion layer, which could not easily answer an auditor who asked what had gone to production and whether it had been tested first. It would be easy to read that as a story about a team that cut corners. It isn’t. Every piece of that machinery resulted from reasonable decisions made by capable engineers who reached for the tools at hand, but the sum of those decisions is a layer lacking the degree of intentional design Lumen puts into their own services. This chapter is the history nobody wrote down: how the layer everyone depends on grew incrementally into something that is difficult to maintain and is not prepared for challenges Lumen never anticipated.

2.1 How Lumen built what it has

2.2 What success cost

2.3 What scale asked of it

2.4 What the layer never had

2.4.1 No view of the whole

2.4.2 Nothing is watching when nothing is running

2.4.3 Nothing shared between teams

2.4.4 Nothing an auditor can read

2.5 A different kind of system

2.6 Summary