Thread by @evanderkoogh

So whenever I rave to someone about @swardley's Wardley Mapping I get asked for an example that isn't a toy example. So tonight I set down to create a slightly more readable version that the scribbled upon one on my desk. Here is @Bitgenics's map:

@swardley Basically companies who want to build web applications for real need a way to get that into production and to host that.
Doing it seriously means Server-Side Rendering & Code Splitting, which requires a server that can handle that. 2/

And that server requires a way to execute JS with a reliable low latency.
And everything requires SPA tech like React, Vue or Angular. 3/

That low latency execution isn’t something readily available. It is Lambda without cold starts and a fraction of the regular latency.

Application hosting around SSR+CS and Application delivery platform are build in-house by every development team. 4/

Last thing to understand is that one of the interesting things is that SPA frameworks are slow to progress to commodity because of the fragmentation of the space.

Soo what can we do with this information?

Come up with game plans! 5/

So, options for actions are: Finish and market the JS engine. Possibility, but really hard to do. People aren’t aware they need it, but you would also quickly end up competing with AWS.
So our best bet here is to wait for someone to do this properly. We do bare minimum needed 6/

Next option: productise the Application Hosting.
Easier to do and also much harder for AWS (or any other of the big provider to follow). AWS is really good at delivering development components at scale, but JS fragmentation prevents them from supporting individual libraries 7/

For a long time that was our strategy, but we had a hard time making that work. Until I realised what we were doing was selling an infrastructure component for the few people building out their build pipelines right now.

What I needed to do was move up the stack. 8/

After I realised I had forgotten what I now call Application Delivery Platform things fell into place. That is something people use directly. Something much easier to sell as a hosted solution.

So then the question became, do I interface with existing CI or roll my own 9/

Realising I had something to offer over the current offering for this nice I decided to roll my own. Over time I might decide to interface with others.

The Version Control System debate was over quickly. Hosted Git is quickly becoming a commodity. Nothing to add 10/12?

So people often ask me if I am afraid of AWS eating my cake and I am not really, because of Wardley Mapping.

We need to drive adoption of a standard to be able to host apps, but we can grow while it is being adopted. AWS can only follow after a certain threshold is on. 11/12

So our strategy is to productise the work being doing in-house in large tech companies and making that available to everyone.

We do that by driving the adoption of a open standard for these kind of apps supported by tooling.

We won’t invest more money in JS execution bit /fin