Marmelab founder and CEO, passionate about web technologies, agile, sustainability, leadership, and open-source. Lead developer of react-admin, founder of GreenFrame.io, and regular speaker at tech conferences.
When your frontend teams are drowning in API complexity and your backend team is overwhelmed with frontend-specific requests, the BFF pattern might be your lifeline. But is it always the right choice?
Lessons learned from GraphQL development: developer experience, benefits and concerns. Is GraphQL a must have, or is it overkill?
Client-side GraphQL is easier than client-side REST because the tools are better. But the additional features (caching, optimistic UI) bring some complexity. Overall, what is the GraphQL frontend developer experience?
In this tutorial, you'll learn the best practices of server-side GraphQL development, based on real-life experience. Covers the basics plus scalability, logging, unit tests, and modularity.
A gentle introduction full of examples and tips for GraphQL, the new way to build web services for mobile.
REST was a great idea, but with modern usage scenarios, it's become slow, expensive, and cumbersome. Do we need to replace it?
Beyond marketing, and because I believe that, in web development, there is no one-size fits all tool, I want to help developers answer this simple question: Is GraphQL a good fit for my next project?
Mastering Digital Craftsmanship
© 2025 Marmelab
