Over on our Adobe blog, Perficient’s Rich Wood digs into the big news announced at Microsoft Ignite that Adobe is making Microsoft Azure it’s “preferred” service:
It’s this simple: Azure is a Microsoft platform, so traditionally when people hear “Azure,” they immediately put walls around it. Those walls look a lot like a Windows server stack and .NET code base. (The fact that Azure is also the name of Microsoft’s cloud development platform doesn’t make matters any easier.) Anyhow, that perception makes sense as far as it goes, but it isn’t true. You can build any sort of architecture on the Azure platform. We’re talking Java-based stuff like Oracle, or even Linux.
This isn’t a widely-known fact, or hasn’t been until lately, and in business perceptions like this can take a long time to change. What it’s meant is that organizations looking at Adobe—which is rooted in Java—rarely if ever considered Azure. That meant Microsoft didn’t have any sort of recommended architectures or specialized Adobe build patterns as a result. You can expect that to be changing soon.
Now, as we mentioned above, Adobe is rooted in Java, and that means this perception factor for Adobe and Azure was a two-way street. Just like shops that were looking at Adobe would dismiss Azure because it’s a Microsoft product, those that leaned to the .NET/Windows stack for their internal applications would dismiss Adobe for their public-facing website for similar reasons. I’ve spoken with many, many clients who in the process of selecting a new web CMS would give this particular fault line an undue amount of attention.
So what does this mean for your company? Check out Rich’s full blog post here.
