OData at Scale: When to Use CDS Views, RAP, or API Business Hub in Hybrid SAP

https://hackernoon.imgix.net/images/A6YHDPuOOaXr23WNPZQiMhegS582-eq03b6e.png

Key Takeaways

● CDS (Custom Transactional Services) views for OData exposure, custom RAP-based services, and SAP API Business Hub published APIs present solutions to different problems that, in a mature environment, should be used together rather than one being the default.

● By transaction complexity, we mean RAP for anything beyond CRUD; by consumer type, we mean CDS views for read-heavy Fiori and analytical use; and finally, by governance, we mean API Business Hub for when an external party is involved.

● Select/filter/$batch tuning changes when traffic passes through the Cloud Connector. For a remote BTP extension, metadata caching and the size of $expand responses usually matter more than they do for a Fiori app running alongside the backend.

● With principal propagation through the SAP Cloud Connector and short-lived X.509 certificates, the hybrid setup can apply backend permissions to each end user rather than routing everyone through one shared...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE

Read more