News Stay informed about the latest enterprise technology news and product updates.

Azure Service Fabric expands outside Microsoft

Microsoft's Azure Service Fabric was created to simplify the creation of highly scalable apps and support massive stateful transactional loads.

In its latest move to catch up in market share and revenue with Amazon Web Services (AWS), Microsoft is launching Azure Service Fabric -- a tool to help developers build highly scalable and customizable applications for the company's Azure cloud platform. It's the latest evidence of Microsoft's expansion of its developer ecosystem, following the debut a month earlier of Azure App Service.

"It's important. It's unique. It's different from every other cloud provider," said John Rymer, principal analyst serving application development and delivery professionals at the Cambridge, Mass. research firm Forrester, Inc. "I don't see anything like this from AWS, IBM or Google. None of them have these service APIs."

Al Hilwa, program director of software development research at IDC, agreed. "This is generally net added value for developers in the Microsoft ecosystem," he said.

As revealed in a blog post by Azure CTO Mark Russinovich, Azure Service Fabric provides a means to build complex, large cloud applications from a collection of interconnected stateless and stateful microservices that use APIs to communicate with each other. Service Fabric has been running in production internally at Microsoft for five years, according to the blog post. It is the foundation technology for Azure's own core infrastructure and is driving several services, including Skype for Business, Azure SQL Database and Bing Cortana. The blog post also explains that the "battle hardened" service fabric technology that Microsoft releases will not differ from the version used by Microsoft's own developers.

I don't see anything like this from AWS, IBM, or Google. None of them have these service APIs.
John Rymer, Forrester, Inc.

 

As Rymer described it, the service fabric is a set of APIs that developers can use to influence Microsoft's cloud operating environment. "What's important is that with these APIs, it is now possible to bring transactional applications to the cloud. Before this, transactional apps were not a good fit."

Historically, stateless applications with scaling worked well, but the introduction of data states that required management necessitated workarounds. "Now, you'll be able to manage states in an elastic environment, necessary for very large-scale transactional apps like retail and even airlines reservation systems," Rymer said.  Microsoft's blog post refers to this aspect, noting support for complex, data-intensive scenarios that can scale to cloud proportions, including -- in Cortana's case -- up to a half-billion evaluations per second. To free developers from the need to re-architect applications as usage grows, Azure Service Fabric incorporates application lifecycle management capabilities.

The release of increasingly powerful tools targeting platform scalability is a key strategy for growing Microsoft's Azure customer base. "It is interesting in that while [Azure and AWS] are increasingly competing for all workloads, and despite a powerful shift toward supporting IaaS, Microsoft is still evolving and investing in its PaaS offering," said Hilwa. "This is important, because such added services can prove to be a differentiator and potentially where more money can be made."

Would a tool with the power of Azure Service Fabric have ever seen the light of day if Steve Ballmer were still running Microsoft? It's an intriguing question.

"It is no accident that Satya Nadella is now the CEO, having run Azure before that," said Hilwa. "Azure has set the pace inside Microsoft for how to aggressively evolve services to harness the cloud opportunity."

Rymer believes Azure's emergence as a power player would have happened under Ballmer, albeit more slowly. "Nadella has a much more open posture than Ballmer. Where Steve had a heavy commitment to the Windows proprietary stack, to Satya, Windows is not sacred." Once Microsoft made the commitment to Azure, the company had to support Java, PHP, and a string of other technologies, Rymer said. "Otherwise, Microsoft's cloud would fail, the world would not come to it, and the economics would collapse. Microsoft had no choice but to open up."

The developer preview of Azure Service Fabric, including educational sessions and live demos, is slated for Microsoft's Build 2015 conference in San Francisco April 29 to May 1. Microsoft plans to make the production version available when it releases the next version of Windows Server.

Next Steps

More on APIs


IT pros size up Microsoft microservice

Dig Deeper on Cloud data integration and application integration

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

3 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Will you try Azure Service Fabric? Let us know.
Cancel
It's always interesting to see how long it takes the marketplace to understand these new offerings that are classified as "unique, nobody else has this in the market". It's not a PaaS platform, but it's sort of an exposure of the guts of a PaaS platform, at an API level. It seems to highlight that structured PaaS models will be attractive to some environments, but unstructured (or less structured and decomposable) sets of APIs will be more attractive to other development groups. It's a little bit like AWS Lambda - sort of it's own product/service category that needs to be understood better.

I wrote about some of that here, http://itknowledgeexchange.techtarget.com/cloud-computing-enterprise/structured-vs-unstructured-paas/, but this sort of takes it to another level by exposing the programming guts as a set of services APIs. 

The next couple of years will be interesting to watch between App Developers and Enterprise Architects as they find the trade-offs between platform lock-in and agility/speed-of-deployments.
Cancel
We would absolutely us the Azure Service Fabric. It's what been missing from advanced Windows Server-side development in the Azure Cloud. If you've been doing advanced WCF and Windows Services ESB-like development and what to migrate your code from the native Windows Server to Azure then it looks like Azure Service Fabric might be just what I've been waiting for. We've been thinking we might have to do it ourselves and the thought of having to do that gave us great pause in continuing with Azure Could based development.

Tavi
Cancel

-ADS BY GOOGLE

SearchAWS

TheServerSide

SearchFinancialApplications

SearchBusinessAnalytics

SearchCRM

SearchSalesforce

Close