Microsoft seems to be paying a lot to buy LinkedIn if you just look at the “P&L” side of the deal.
But if you examine the long term MSFT strategy of making Office 365 thepervasive business and social platform for documents, presentations and spreadsheets, then it makes the deal worth the investment cost.
In doing work for a local healthcare product venture, I was asked to look at the network and database requirements to support mixed content transactions, video streaming all while conforming to HIPAA compliance standards. As a part of this work, I developed a Web Services Cloud-based architecture that took into account, ERH, HL7, document management and provider notation.
This tasking led me to a deep dive on the data architecture and DB requirements analysis that was required to develop the architecture.
The question of utilizing standard RDBMS (SQL) VS NoSQL was an immediate consideration. My conclusion…. It depends on a large number of technical, business and regulatory factors to derive the appropriate architectural answers. For example, what other external systems are interfaced to the applications and how do they require interaction? In general with the prolific growth in web services, mobile and cloud computing today’s enterprise will require a polyglot data architecture to satisfy all stakeholders.
A look at Healcareinformatics provides an operational insight into some of the complexities.
“Healthonomics” can be the key driving factor to trigger enterprise decisions to support multiple types of DB solutions woven together in a heterogeneous way delivering a network of web services that affect healthcare outcomes.
As we start to see the uptake in 4K video content, suppliers of CPUs, NIC (Network Interface Cards), networks (LAN, WLAN, Wi-Fi) and storage technologies will all be struggling to “step up to the plate” in meeting the challenges of this disruptive Video format. Also IAAS platform providers will face huge challenges to configure cloud components that can be rapidly provisioned for 4K content or Video Streaming. Even the security industry will be affected regarding the video surveillance infrastructure (see this Video Security Magazine article).
This is a Technologies Strategic Directions “Sleeping Inflection Point” for multiple industries, manufacturers, eworkers and information consumers.
Ultra-high definition (UHD) resolution is 3840×2160 Pixels now used in displays and broadcast., This does not equal 4K (4096×2160 Pixels) used in digital cinema. People tend to used them interchangeably but there is a significant difference in impact on the networking bandwidth required to service consumption of 4K.
We all are aware from a display technology perspective that TVs are now offering this content. However, how about other network and computer infrastructure components? When will they be able to handle the disruptive impact of 4K?
A recent article of an interview with the Red Hat CEO touts the benefits of private cloud implementation. See it at HERE
This debate is usually short sited and doesn’t include all CAPEX & OPEX cost associated with the “Free OS” type of cloud operations. Also the reusable components from more sophisticated partner communities afford both AWS & AZURE much greater long term valuations when responsible Enterprise accounting methods are used to drive the cost benefits analyses. The proper engineering of a cloud infrastructure which includes smart VMs well orchestrated by business-demand-level-driven auto scaling will always push the TCO/ROI argument to a public solution for large scale systems.
Microsoft actually has a TCO tool that they can use to estimate TCO of on-premises vs. Azure. There are many considerations when comparing costs of running an on-premises datacenter with full infrastructure, servers, cooling, power etc to a cloud-based service like Azure where you pay a cost based on the services consumed such as storage, compute and network egress. It can be difficult to know exactly what typical costs are for your datacenter and what the costs would be for services running in Azure. Microsoft has a pricing calculator available at http://azure.microsoft.com/en-us/pricing/calculator/ which can help access costs for Azure services and a VM specific calculator at http://azure.microsoft.com/en-us/pricing/calculator/virtual-machines/.
When running on-premises, you own the servers. They are available all the time which means you typically leave workloads running constantly even though they may actually only be needed during the work week. There is really no additional cost to leave them running (apart from power, cooling etc). In the cloud you pay based on consumption which means organizations go through a paradigm shift. Rather than leaving VMs and services running all the time companies focus on running services when needed to optimize their public cloud spend. Some ways that can help optimize services running are:
Auto-scale – The ability to group multiple instances of a VM/service and instances are started and stopped based on various usage metrics such as CPU and queue depth. With PaaS instances can even be created/destroyed as required
Azure Automation – The ability to run PowerShell Workflows in Azure and templates are provided to start and stop services at certain times of day making it easy to stop services at the end of the day then start them again at the start of day
Local Automation – Use an on-premises solution such as PowerShell or System Center Orchestrator to connect to Azure via REST to stop/start services