Skip to main content

Why Windows Azure is on Cloud 9?

Cloud computing market is crowded with more and more vendors as it is seen becoming no.1 in the ‘what’s next’ list among the CEOs & CIOs. Google, Amazon, Microsoft are pioneers in this arena. Based on my observations, I can see more tractions on Windows Azure based enterprise apps. There may be many reasons. One key reason that would have made Windows Azure as one of the key choice may be ‘data storage’ facilities it offers.

If you see the key players in cloud computing viz Amazon, Google, Microsoft, they are offering data stores based on EAV model:

• Amazon – SimpleDB

• Google – BigTable

• Microsoft – SQL Data Services

EAV models are suited only for the scenarios where vast no. of attributes is used to describe an ‘Entity’. From the business domain perspective, ‘Health Care’ can be a good candidate for such scenarios. Especially when data models are designed for the databases to store info on clinical findings, we will end up in lots of attributes. If we design database models for such info based on relational database principles, we will end up in tables with thousands of columns and it will end up in many overheads and underperforming systems. For such scenarios, EAV based data storages are appropriate. So, when we design and develop a cloud application for Health Care, it is best to leverage the EAV based storage systems provided by the cloud vendors either it is SimpleDB or BigTable or SQL Data Services.

For the applications such e-commerce or banking where we don’t see much variation in attributes of entities, EAV will not work. RDBMS based storage is the best option for such applications.

Unlike the other vendors, Microsoft provides first relational database model based cloud storage called ‘SQL Azure’, in addition to EAV model storage ‘SQL Data Services’. Developers can leverage their existing skills on T-SQL, SQL Query, stored procedures etc.

So, for applications like e-commerce or banking where EAV may not appropriate, Windows Azure stands as the first choice because of its support for relational database model.

With the opportunities for leveraging developers skills on Visual Studio and conventional SQL based data access techniques, cloud computing may not look much different for the developers. Their lack of knowledge on EAV concepts will not become stumbling blocks in their development journey. Adding to that, SQL Azure also allows SQL developers to migrate the data from their existing RDBMS databases without any major effort.

With the fact that not all applications to be made ‘Cloud’ aware are should be based on EAV models, I think we have justifications to see Windows Azure as the front runner in cloud platform.

Let us wait & watch :)


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…