Centralised Data Storage : Apps? or traditional .NET with SQL Backend?


hi all,

perhaps bizarre question i'm looking definitive answer above.

buy in whole "apps" idea being isolated, nice easy life-cycle , clean mechanism .... struggling see how scale in enterprise:

example, of see appears "apps" performing specific, simple task , sharepoint components deployed working data installed app-web such multiple installations @ different site scopes leads proliferation of multiple "instances" of data definitions.  explained nicely in "surveys" example here :-

understanding sharepoint apps

my question therefore around scenario data maybe more complex, high-volume , transactional.  practice build out lists , libraries in specific site collection centralised usage (let's assume "expenses") ... , develop "app" deployed anywhere app catalog - accesses "centralised data repository" installed instances read , write same lists?

i'm starting suspect *not* apps should used , looking clarification.  clearly, type of design involves specific relationship between app , data , 1 cannot controlled given explicit separation?

with approach, find i'm battling permissions since, if user not have write permissions site lists reside, app cannot write on behalf of user (sharepoint hosted) .... , provider hosted gives me issues when using app permissions since cannot id of current user in site if user doesn't have permissions in first place.

appreciate there's lot of words above ... guess simplify question - if i'm looking work common centralised data source, should use sql server mvc / mvvm design pattern , leave apps simple / repeatable / "disconnected" type of operations?

here's 1 of issues i'm facing , it's last response dragan leads me ask this.... trying shoe-horn sharepoint doing isn't designed do?

list permissions auto hosted app

thanks

steve



imho, apps solution reusability... far expenses go, allowing each site/subsite/etc have own expenses app (analogous phone having multiple apps different notes / contacts / etc).

as far enterprise needs , integration, have few options...

1. app designed multi-tenancy, roll-up capabilities... applicable more azure hosted app, app responsible managing data more sharepoint.

2. app store data in each site, , etl applied across orgs. analogous etl between data marts , data warehouse

generally speaking, use app model few limited cases:

- office 365 tenant

- productization

- if makes sense multiple instances of same app exist in single site (not subsites)

otherwise, leverage sp ecosystem in other ways...

- single app/site enterprise use, reduces instances of data. since development occur once, use of app or other sp solution may unnecessary if client-side options sufficient. in case, upgrade model exceptionally simple.

- if data massive store internal sharepoint, use bcs against sql backend. should not default, since sp's core cms capabilities need implemented (versioning, recycle bin, etc) within sql backend.

scott brickey
mcts, mcpd, mcitp
www.sbrickey.com
strategic data systems - sharepoint needs



SharePoint  ,  Apps for Office and SharePoint  >  Developing Apps for SharePoint 2013



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more