Skip to main content

Common Show Stoppers in Enterprise Applications Rollout

In any of the Enterprise applications / systems development, the issues that we face can be categorized across following 4 categories :

1. Environmental issues

a. "In UAT environment it is production it is not working " [Because of mismatch in the versions of the softwares installed, Hot fixes applied , Patches updated, some files corrupted , Mismatch in the keys used while using encryption / decryption, registry issues because of some corruption, inconsistency in configuration (DB server, APP. Server etc.) – sanity issues]

b. "Yesterday it worked.Today it is not working " [May be it is tested with some other data…today with a different data, Un-audited software installations etc.]

c. Some times bugs in the platforms will get revealed only under some circumstances which even platform vendors may be un-aware of !

2. Resource Availability
    [This may lead to non-reproducible errors and hence affects reliability]

a. Availability of DB connections / other legacy resources
b. Thread pool

c. RAM, CPU etc.
d. Instability in the availability of the common resources (which are also used by other applications )
e. Shortage of the resources in the peak loads.In this case problems will bubble only in the peak stage. We will not be able to reproduce it hence it will lead to lots of confusion

3. Resource Accessibility

a. Access to some resources is limited to some roles – DB connections , User roles not mapped / configured in the legacy resources
b. Some times there will be a policy because of which password will get expire / reset
c. Missing of credentials synchronization across resources

4. Interoperability

a. Types exposed through a service cannot be consumed by a client application developed in a different platform
b. Data types adopted by the data access layer not compatible with the Database system

If we can have processes / policies / governance that are devised around these categories; if we start any development with the consciousness of these factors in mind, then any enterprise application rollout will be a smooth ride and will not result in unnecessary, un-productive night outs & escalations.

In addition to these categories of issues, we will always face issues related to Non-functional requirements like Performance, Security etc. Those issues will surface only under certain architecturally significant scenarios & special conditions. That too, they will bubble only on the final stage of testing & deployment.


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 ...

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, & StreamInsighthave rich set of adapters minimizing the development time), Partner ecosystem with solutions(like what partners have solutions basedon 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 a…