For us the primary value is behind the customizability of it all. One of our main requirements is to give user A LOT of flexibility to customize the default fro

For us the primary value is behind the customizability of it all. One of our main requirements is to give user A LOT of flexibility to customize the default frontend to suit their needs. On top of that we are running DDD in the backend with ARs being spread over multiple different services. We did experiment with rest early on, but we found out that we would need to make our frontned to be extremely complicated and vocal to handle the customization/data fetching requirements or build our own REST gateway on top of open API, doing, essentially, the same thing that graphql gateway does out of the box. Adopting graphql was scary at first with low team exposure to the technology, but using REST would have made our life much much harder