How do i choose between a single complex api endpoint and multiple simpler ones?

[ElizabethFT]

I'm trying to decide if I should use a single, more complex endpoint that returns everything my app needs or break it into several simpler ones. The all-in-one approach feels efficient for the client but makes the server logic heavy and caching tricky.

[Stephen77]

I started with all in one. It felt slick until caching blew up and the server got bloated trying to assemble everything.

[EleanorLT]

We broke it into smaller pieces and suddenly caching got predictable, and we could deploy parts without touching the whole thing.

[James45]

Sometimes the issue isn't the number of calls but the data contract; small changes ripple through all the dependents, no one's happy.

[GraceJ]

I keep thinking we might be chasing speed over resilience, and I'm not sure the problem is the calls at all. Do you think the real bottleneck is something else?