Skip to Content
Jan 14, 2020 at 07:13 AM

From Olingo to Cloud SDK: make sense?

4714 Views Last edit Jan 14, 2020 at 07:14 AM 2 rev

Hi community!

I'm trying to understand if it would be convenient for me to "update" my way to develop oData services in Neo environment... Actually, I'm using Olingo 2 library with JPA Processor, so it is easy for me to create entities and access related table via oData services (CRUD operation automatically managed by Olingo library).

I'm trying to understand if it would be worth for me to use SAP Cloud SDK; from what I read, I could be interested in:

  • oData vModel (now I'm using other Java libraries to consume external services, such as UNIREST);
  • Resilience / Caching / Other cool functionalities;

Issues (fully related to my actual situation, not general issues):

  • CAP could not be used in NEO, from what I know;
  • I do not want to re-implement all needed CRUD operation already exposed automatically via Olingo;
  • I do not want to use oData v4 because I cannot adapt all front-end applications already developed;

I found lot of references to oData VDM (the way to consume oData services) in SAP Cloud SDK; not so many references, instead, explaining how to expose an oData v2 service; It seems possible with SAP Cloud Platform SDK for service development (no recent references, by the way... Now it should be included in CAP); Reference:

So my questions at the end:

  • Is there some documentation somewhere on how to link entities to odata v2 in SAP Cloud SDK (just as in Olingo jpa processor)? With SAP Cloud SDK it seems easy to write your own handlers, but nothing will be done automatically, am I right?
  • In this specific case, it is worth not to use Olingo and use the SDK?
  • Why should I use oData v4? Which are the advantages respect to Odata v2 both in back-end (Java application) and front-end (Fiori) applications?

I hope you could help me in understanding the big picture,

Thank you so much!