API Gateway: Should we centralize logic, or spread the responsibility around?

hey everyone, i've been thinking a lot about api gateways lately. we're considering implementing one to manage our microservices, but i'm torn on how much logic should live within the gateway itself. should it handle things like authentication, rate limiting, and request transformation centrally, or should those responsibilities be distributed closer to the individual services? what are your experiences and opinions on this architectural trade-off