CODEWITHSUNDEEP
c#ado.nethana
Shubha Lakshmi
Shubha Lakshmi

Reputation: 137

Using SAP HANA Extended Services (XS) versus ADO.NET/C# for application development

Would it be better from an application developer point of view to use native XS engine which is tightly coupled with SAP-HANA database, rather than using ADO.NET for connectivity and using ASP.NET/C# for application development ? Which would give me more options for leveraging SAP-HANA DB and better performance.

Upvotes: 0

Views: 953

Answers (1)

Abdel Dadouche
Abdel Dadouche

Reputation: 217

The HANA XS engine is natively integrated with SAP HANA, therefore it can only provide you with benefits when interacting with HANA.

For example, the data access will be easier and faster as you won't need to pull the data out via the ODBC/ADO layer but rather consume it "locally".

With SAP HANA, you can run it all in one place which will free you from the network latency for example.

It's also comes down to an architectural discussion, where you can/want decouple your data (model), your logic (controller) and your ui (view) and use use an heterogeneous stack or not.

The XS engine provide you all 3 in one place.

The XS syntax is really similar to JavaScript and inherits a lot from it (if not all).

Then also comes the reason why you would use JavaScript compared to .Net/C# which reflect the client-side vs server-side execution dilemma.

JavaScript can do both (and even more with the rise of Node.js), but I'm not sure you can achieve that with ASP.NET/C#.

Anyway, as I work with/for SAP, my opinion might be biased (just a little sometime) but I hope it will give you some food for thought.

Upvotes: 1

Related Questions