Pourquoi ne pas utiliser SharePoint 2013 comme juste un backend pour les clients REST / CSOM?

Question

Cela peut sembler extrêmement extrême, mais maintenant que les API de repos / CSOM sont plus entièrement en vedette, pourquoi ne pas simplement écrire des applications Web dans n'importe quel cadre que vous êtes à l'aise et utilise les API de REST / CSOM au lieu de vous déranger avec la programmation byzantine de SPTechniques de modèle et de marque?Les applications doivent-elles être impliquées du tout?Qu'en est-il des situations croisées?

Donc, si je suis plus à l'aise à l'aide de la pile MS, je pouvais écrire quelques applications MVC ASP.NET à l'aide de l'API de repos pour la communication latérale du serveur dans C # et CSOM dans le navigateur à l'aide de JavaScript.

Answer 1

If what you want to do can be done using REST / CSOM, then by all means, go for it, that's what MS is aiming for with the app model. Not everything that can be done using Server object model & farm solutions etc. can be accomplished that way, however.

If your question is why not just use SharePoint as your back end and not use the UI and re-write a whole web app on top of that, then perhaps you should just skip SharePoint and use a DB as your back end.

Answer 2

There is a hybrid approach where you use SharePoint's documents storage, lists, workflow engine, account authentication/authorization, and web services with a highly customized UI. James Love mentions this in his comments to Igaud's answer.

I have found this approach to be very successful, especially to users who for some reason have a bad taste in their mouth from a previous, poorly architected SharePoint deployment. This approach gives the developers full control over the UI and can really increase perceived performance while helping the developers to rapidly develop highly customized line-of-business applications without having to build their own services, account management, content management systems.

Answer 3

With PS2013 and app model, you are essentially building a solution outside of SharePoint (provider hosted, or auto hosted) and then utilize the OAuth and cross-domain integration infrastructure to access SharePoint data. You could use any technology stack that you want here, and then rely on either JavaScript CSOM or SP REST API to accomplish your goals.
If you goal is just to build a data driven application, then SharePoint should be your persistence layer just because; it's a huge overkill.