But that’s an argument from tradition. I’m not saying I disagree with you, at my company we use CSS modules (which can be considered as CSS-in-JS, although I don’t see it that way). For us it solved a mess of CSS that had grown over the years, where the original plan was lost and different people were afraid to remove code because they were unsure…
I have a hard time convincing coworkers of this. They see it as adding a single point of failure. So what we do is that each of our micro frontends also implements its own GraphQL server.
Do you have any tips on how to convince my coworkers that this approach is better?
Nice writeup. We are in a similar process, moving from a .NET monolith to a React/GraphQL/NodeJS stack for our front end.
We started with Redux, but switched to Apollo GraphQL because it makes it so easy to use multiple micro services in a single query. We haven’t implemented Engine yet, but from your story it seems quite valuable.