And thus was born the service-oriented architecture.

No, that's multiplayer.

Not sure why you're downvoted- that's how my friends and I would play multiplayer, with certain players taking "ownership" of specific raw material sources and shipping them to factories operated by other players.

Yeah, bootstraps all the way: 1. Bootstrap "base 1" to Automation 1 (Coal etc.) 2. Bootstrap "Base 2" for Red/Green science, automate building components 3. Main bus "Science Base" maybe up to first rocket (maybe some train in resources) and later repurpose for module construction. 4. Train Base to goal SPM factory

The game has some major transition points where refactoring makes sense, but often the correct solution is to tactically upgrade as much as possible, and get to the better point to rebuild.

Seablock playthrough once updated for 1.0.

"Build one to throw away"

Somewhat, but also build a new one while letting the old one still perform useful work, decommission when it is beneficial.

All bets are off in seablock.

Lol this is what a company I worked at did and they spent almost a year trying to get version 2 to parity with version 1 and finally gave up short of parity

In the manufacturing industry that's basically drop shipping.

More like if a manufacturer needed to make a new product so they built an entire new factory next door and ran electric and plumbing from the old building and abandoned it.

In fact it's exactly like this because that's what the game is about.

The game has logistics drones that can transfer predetermined resources to keep a certain box at a certain level.