cancel
Showing results for 
Search instead for 
Did you mean: 

Web app development

dan_benamar
Explorer
0 Kudos

I'm about to start working on a large web app that is to be connected to SAP Business One.

This is something I'll be later installating on many costumer sites (on-premise) and in cloud environemnts.

My development platform is ASP.NET MVC (Visual Studio 2015).

Due to the solution targeted to small businesses (1-10 seats mainly), the target version of SBO is the SQL version.

I'm not sure which way to go in regards to the connection.

From what I understand:

  • DI API is not recommended for use in web application (slow, unreliable).
  • DI Server is being phased out, and there is no HANA version.
  • The Service Layer is only available in the HANA version.
  • B1i is only suitable for integration and not intended for my use.

I'm sure that for the next few years my target audience will not be using HANA but want to make sure I have a clear upgrade path to utilize it within 2-3 years.

How would you approach this.

Thanks, Dan

Accepted Solutions (1)

Accepted Solutions (1)

pedro_magueija
Active Contributor
0 Kudos

Hi Dan,


DI API is not recommended for use in web application (slow, unreliable).

Always measure, but I think your main problem with be the licensing scheme (not really adequate for Web applications).


DI Server is being phased out, and there is no HANA version.

According to your need it could be adequate, until you find it necessary to migrate to say the Service Layer or B1if.

The Service Layer is only available in the HANA version.

Yep, your statement says it all, but if in the future your target audience is in HANA this would be the way to go.

B1i is only suitable for integration and not intended for my use.

I heard that you can create web services using B1i that could be used by your web app. (In any case you should check this out: Creating Web Services with B1if and Consuming b... | SCN). There are youtube videos as well.

In any case my main advice is that, it's clear that you'll have changes in the future regarding the backend of your application so one great advantage you can give yourself is to decouple your application/frontend/domain from your backend, and when the time comes swap the backend implementation for a more adequate one.

Cheers.


Best regards,

Pedro Magueija


View Pedro Magueija's profile on LinkedIn

Answers (0)