3 ms·
Remix seems to be a counter-example. The jokes app tutorial [1] is as monolithic as they come. [1]: https://remix.run/docs/en/v1/tutorials/jokes https://remix.
by mwcampbell 4y ago
Remix seems to be a counter-example. The jokes app tutorial [1] is as monolithic as they come.
[1]: https://remix.run/docs/en/v1/tutorials/jokes https://remix.run/docs/en/v1/tutorials/jokes
- dfee 4y agoMonolithic – yes. However, my concerns with Remix are that it intentionally doesn't align well with the premise of GraphQL – for better or worse. However, that's a very common pattern when you do need microservices. I.e. Remix doesn't have a good story for off-boarding from a monolith – so it's inherently risky to build on top of. GraphQL really isn't that hard, and if I'm going to build an API anyway, why not just start with a piece that's going to eliminate the endless refactoring of data-stitching when the needs of my pages (or underlying components) change?