SharePoint 2013을 REST / CSOM 클라이언트 용 백엔드로 사용하지 않는 이유는 무엇입니까?

Question

이것은 조금 극단적 인 것일 수 있지만, 이제는 REST / CSOM API가 더 완벽하게 추천되어 있기 때문에, SP의 비잔틴 프로그래밍과 함께 괴롭히는 대신에 REST / CSOM API와 편안한 프레임 워크에 쓸모가없는 어떤 프레임 워크에 웹 앱을 작성하는 것이 아닙니다.모델 및 브랜딩 기술?앱을 전혀 포함해야합니까?도메인 교차 상황은 어떻습니까?

MS 스택을 사용하는 가장 편안한 경우 JavaScript를 사용하여 브라우저에서 C #과 CSOM의 서버 측면 통신을 위해 REST API를 사용하여 일부 MVC ASP.NET 응용 프로그램을 작성할 수 있습니다.

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.