Skip to main content

Flexibility through product customization - How Secured it is ?

When providing solutions based on the multiple products, the success of the solution depends on what level of OOB features of those products helps in addressing the business / functional needs and what level of flexibility those products offers in terms of customization.

Also, how those products help in addressing business needs is very important in terms of time-to-market through:

  • Capabilities for seamless integration with federated business partners through adapters (like what Microsoft BizTalk, & StreamInsight  have rich set of adapters minimizing the development time),
  • Partner ecosystem with solutions  (like what partners have solutions based  on SharePoint in addressing various business requirements such as document storage, DRM / IRM, BI etc)

 
In addition to above mentioned factors, success depends on how the products allow developer community in extending its capabilities to address complex techno-business requirements.

 
While allowing the developer community for customization, it is also very important how a product provides capabilities for the secured execution of those custom code blocks – at the same time, without affecting the performance of the application and without allowing the code blocks to block resources – CPU, RAM, Threads etc. – especially in the scenarios of “careless “/ malicious code blocks, bringing down the entire application execution environment.

 
SharePoint is one such product that allows developer community to address complex techno-business requirements and other needs of an Enterprise through extensive customization and also ensures reliability of the application through “Sandbox” – secured code execution environment.

 
In addition to secured code execution capability, for the developer community, it is a must for the availability of the sophisticated tools for carrying out post code engineering activities such as performance tuning, code profiling etc.  Microsoft development platform provides tools for carrying such activities on SharePoint customization code blocks that are marked for Sandbox environment

Comments

sirking said…
I am extremely cheerful to find your post as it will get to be on top in my accumulation of most loved websites to visit. about this

Popular posts from this blog

Lambda Architecture on Microsoft Azure

Gone are those days when Enterprises will wait for hours and days to look at the dashboards based on the old, stale data. In this fast world of BYOD, fitness gears and flooding of other devices, it is becoming super important  to derive out “actionable” information from huge volume of data / noise that is generated from these devices or any other data sources and act proactively on them  in real-time, to stay competitive.

At the same time, the need for having dashboards and other analytical capabilities based on the quality, cleansed, processed data still very much exists.

With the emergence of more data types and need to handle huge volume, shift is happening from the conventional data warehouse practice to cloud based data processing & management capabilities where high volume batch processing is possible at the optimized cost. Business scenarios demanding the need to process the data in real-time   More

SharePoint 2013 Architectural Trade-Offs

When planning for deploying SharePoint 2013 based Enterprise workloads, it should be done with the consideration / awareness of impact of various architectural decisions what we make. As SharePoint 2013 is a flexible platform providing lots of options in terms of configuration of the existing OOB features and development of custom development solutions to address specific business functional needs, care should be taken when making a particular decision and its impact on overall solution. Even though SharePoint is a matured product, the effectiveness of various business capabilities such as Enterprise Social, Enterprise Search, BI, Document Management, Web Content Management, and Enterprise Content Management that will be delivered based on it, in terms of addressing the business requirements depends on architecture planning. Effectiveness here means performance, security, up-time and other architectural qualities like Scalability, Reliability etc. more ...

Heterogeneous Cloud Integration

Heterogeneous integration is common scenario in the Enterprises where their IT portfolio is based on heterogeneous platforms. Various solution approaches such as message broker, messaging middleware, SOA – service based integration were employed to address heterogeneous integration challenges.

These solution approaches were good when the integration happens on premise, with in the data centers of an Enterprise. Problem here is non-availability of “elasticity”.

With the Enterprises started leveraging cloud platforms extensively for various solution aspects such as elastic computing, storage, it opens new capabilities that can be leveraged for heterogeneous integration. Also, similar to existing on premise scenario, Enterprises are also leveraging multiple cloud platforms to address their business needs. This scenario will pose same integration challenges as those that were faced within on premise datacenters

Within datacenters / on premise, integration products were expected to comply wi…