Sure, basically we have a standard microservices architecture and sometimes the needs of the frontend team and backend teams aren't aligned. For example, search

Sure, basically we have a standard microservices architecture and sometimes the needs of the frontend team and backend teams aren't aligned. For example, searching UX or Pagination UX needs are classic examples where scalable apis use cursor pagination but frontend UX needs offset pagination. So in many cases frontend UIs make a huge number of api calls across a number of microservices to render a single view (classic graphql use case) and end up caching a view of the database in the browser to implement filtering. So I’m looking for perspectives on building a backend for frontend team implementing some APIs specifically for frontends that does the work of stitching together backend api calls from many microservices.