[cateye]

I have mixed thoughts about this approach.

Unification should mean creating a single interface that seamlessly interacts with multiple underlying services without needing custom adaptations for each case.

The issue with allowing for customization is that it leads to fragmentation. This defeats the purpose of having a unified API in the first place.

I'm not sure whether the convenience of unifying leftover common functionalities like authentication outweighs the complexity and reliance introduced by adding another layer to the tech stack.

[bastienbeurier]

These are all fair points!

In practice, most customers we serve have use cases that could not be supported by traditional unified APIs, but are still better off not rebuilding an integration infrastructure from scratch.

We also offer professional services to outsource the customization, so you still have an off-the-shelf unified API, but specific to your company.