Why are our Sharepoint apps so much slower and harder to use than the other .net MVC apps?
Why are the sharePoint created apps so much slower than the regular web bases MVC .net apps?
We are trying to come up with some guidelines for what works for SharePoint 2016 and what does not. We are running SharePoint 2016 on premise.
According to Microsoft, we should be using web parts, then sending JSON off to a business layer like Azure Functions.
From what I gather web parts are a combination of HTML and jQuery, then you kinda fit them together like puzzle pieces. The web parts then send the data off to c# (or any business layer) server as JSON, then magic happens. I am also assuming since the c# is mostly stand alone, we can write the data to any database and this does not have to be a content database.
So my understanding of all that is correct, why is it that every app I demo from our dev team is SOOO much slower than any other HTML / jQuery app that talks to a database?
Maybe my understanding is flawed and I am aware of that. I would greatly appreciate if somebody can point me to a URL or book that discusses where to stop using Sharepoint and just build a native MVC app, that would be awesome!
What is SharePoints best use case? I keep hearing it can do everything, but let's be real, nothing can be good at everything.
Thanks experts!
We are trying to come up with some guidelines for what works for SharePoint 2016 and what does not. We are running SharePoint 2016 on premise.
According to Microsoft, we should be using web parts, then sending JSON off to a business layer like Azure Functions.
From what I gather web parts are a combination of HTML and jQuery, then you kinda fit them together like puzzle pieces. The web parts then send the data off to c# (or any business layer) server as JSON, then magic happens. I am also assuming since the c# is mostly stand alone, we can write the data to any database and this does not have to be a content database.
So my understanding of all that is correct, why is it that every app I demo from our dev team is SOOO much slower than any other HTML / jQuery app that talks to a database?
Maybe my understanding is flawed and I am aware of that. I would greatly appreciate if somebody can point me to a URL or book that discusses where to stop using Sharepoint and just build a native MVC app, that would be awesome!
What is SharePoints best use case? I keep hearing it can do everything, but let's be real, nothing can be good at everything.
Thanks experts!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks experts.
Thanks
ASKER
I am not sure Sharepoint will replace apps for a specific use case. I am guessing they are better for the more generic use cases with lots of changing requirements.
Thanks for your input. This stimulated a lot of great thought.