These are chat archives for jdubray/sam
In general Microservices Frameworks aligned well with SAM because SAM enforces a single state tree (Model). The Model can then decide the best course of action (so to speak) to persist itself via Microservices.
SAM also allows you to write isomorphic code trivially, so you can debug your code in the browser (Actions, Model, State) and then move it to Node when you are ready, just by changing a couple of lines of code on the client.
Here is an example with Node.js
The problem with React is that they built it for Facebook and completely missed the point that you need somehow to weave API calls into your front-end architecture. So they ended up kicking the can and created GraphQL+Relay. I would stay away from React altogether, unless you have the same problem as Facebook you are trying to push as many CPU cycle on the client (when you have 1.5B users you never want to waste to many CPU cycles on the server)
I would say, there is no need for pattern matching with SAM.
The problem is that once you take the wrong turn with factoring, you enter a maze that you can never get out.