The Nine Systems acquisitions places Akamai in the role of an emerging service layer to those media companies aspiring to become Internet distribution and advertising powerhouses, not just content creators that feed other distribution networks.
Analyst Dana Gardner examines IT news and trends that impact software strategists to provide insights and outcomes on SOA, app dev, SaaS, enterprise infrastructure and mobile convergence.
Dana Gardner is president and principal analyst at Interarbor Solutions, an enterprise IT analysis, market research, and consulting firm.
Oracle's been trying to get into this operating system space for a long time. In the past decade, they were one of the aggressive promoters of the whole network computing concept, where theoretically you wouldn't be relying on a fat client, so to speak, meaning Microsoft Windows. You could access all your applications via some type of thin client or network computing device.
Seems the communities are not keen on the details of the agreement, but at least Microsoft and Novell seem intent on reworking the issue. Of course, the need to clean it up lends credence to the notion that they rushed this thing. And why? Was it the Oracle-Red Hat bombshell?
Several new Eclipse-based projects are emerging that provide a strong framework for device development, and the theme is a common framework everywhere. Indeed, the mash-up of open source Java and Eclipse is very exciting. This new Eclipse activity augments and burnishes the Java ME platform, especially as its runtime (if not the community and tools) go GPL open.
Go independent, and stay independent, and federate on terms that favor the content providers, not the mall owners. Go United Artists, down with MGM (circa 1938). Long live the micromedia companies, not those who wish to squeeze them in the name of getting attention.
Yes, Intel has become the best new sugar daddy for Web 2.0, and the obvious new best greased skids for taking the concepts uptown to the enterprise. Cool.
Is there a defacto standard in the making for how to best use open source in a SaaS model that does not leave the provider open to code and revenue hi-jacking? My thoughts have been that SaaS providers should use OSS as platform and deployment infrastructure alone, while keeping the applications as their intellectual property. That both reduces risks and total costs.
BriefingsDirect SOA Insights Edition, vol. 3: Gardner, Garone, Ward-Dutton and Pendleton on SOA, open source, and making the business case for SOA
How should we evangelize and educate the concept of SOA as strategic, as architecture, as a long-term approach, when we’re still stuck in kind of a tactical decision-making process, and we have a variety of different vendors, and open source projects approach to componentry on the tactical level? The panel sees the business case as essential, but not necessarily by calling it SOA. Where's Steve Jobs when you need him?
A developer writes that he sees more income in his future by developing in Visual Studio and, via Mono and blessed by the Novell-Microsoft pact, deploys easily to Windows or Linux. He says that Microsoft just waited for Linux to gain sufficient market share for them to begin to monetize it, in addition to Windows, albeit at lesser margins.
The real end-game for open source then is the rest of the stack, right up to and including the business applications. The new questions are: Will the JBoss model be repeatable and allow Red Hat to successfully move up the stack? Can they do it without IBM and Oracle? Will SOA emerge as a strong open source alternative? Will the hardware providers begin to give away the software, ala Sun, to pressure the non-hardware software players on price and make the profit from the hardware alone? Will the SaaS providers squeeze the business applications profits even as the profits in the Linux bottom of the stack wither?