Complex modelling of oData with huge number of entities and attributes

[jesonsabin_lawrence]

Do we have any recomendation on the size of the oData services. Can i model a very complex data model like the customer or supplier which could have around 2000 attributes with around 100 entities in a single oData service?

what would be the implications on the CUD operations?

[kammaje_cis]

Hi Jeson,

I wonder what would be the use-case for such a big service with 100 entities.

Since the metadata is cached at various places, performance may not be impacted that easily. (https://help.sap.com/saphelp_gateway20sp06/helpdata/en/3d/45e259b4bd49e197316cbfd3c7fa8e/content.htm)

One thing you need to keep in mind is that regression testing. One service is made up of one Data Provider Class and One Model Provider Class.  Having 100+ entities means that you might have used this service in many frontend applications. So any change to any of these two classes would make you regression test all your applications,

I would create separate services based on logically related entities.

Thanks

Krishna

[ChandraMahajan]

Hi,

I will refer you to below links first.

• Performance Best Practices - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library
• OData Best Practices - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library
• and Creating High-Quality OData Services - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library

As per best practices docu, Don't use a large number of properties.

As you are saying around 2000 properties and 100 entities, it will be too much complex OData service and it will loose the advantage of REST based service.

Regards,

Chandra