为什么不使用SharePoint 2013只是休息/ CSOM客户端的后端？

Question

这可能听起来有点极端，但现在REST / CSOM API更全面的特色，为什么不仅仅是在您对您感到满意的框架中编写Web应用程序并利用REST / CSOM API，而不是使用SP的拜占庭式编程模型和品牌技术？应用程序是否需要涉及？跨域情况怎么样？ 因此，如果我最舒服地使用MS堆栈，我可以使用JavaScript在C＃和CSOM中使用REST API编写一些MVC ASP.NET应用程序，使用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.