Our customers have become more mobile as their businesses have grown, and their lives converge with their day-to-day work activities. So we find a lot of customers are using our mobile capabilities to extend their flexibility and productivity outside of work.
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.
The SCA/SDO backers invited Microsoft to join their efforts, they said, to adopt a programming-level of SOA standardization, rather than a Web services level of interoperability. But the members voiced little hope that Microsoft would have a sufficient motivation to move .NET to a programmatic open standards level. SCA/SDO is nonetheless expected to make interoperability between .NET- and non-.NET-based services a natural and rudimentary aspect of SOAs, but at a higher cost -- a tax, if you will -- due to Microsoft's separation from the pack.
We took a much broader view to say that the bus is really all of your XML, HTTP, and JMS -- all of your communications -- and it encompasses a variety of clients and servers and different endpoints. So what do you need in that space? You need a very smart and simple mediator that can fit in, without disturbing those existing systems, and add those levels of management, connectivity, and virtualization that I was just talking about. That was really our plan and our approach to this space.
IBM has been on a buying spree for development prowess, what with Build Forge, WatchFire and now Telelogic coming under the Big Blue umbrella. But if IBM wants to dominate enterprise development of the future, and is wondering how to better bring Web 2.0 to the enterprise, wouldn't an Adobe-IBM mash-up make a huge amount of sense?
So IBM can say otherwise, but I see IBM as in the applications business of the future, top to bottom. ISVs don't necessarily have to quake in their boots, but the enterprises and end users that need solutions, regardless of the code approach, should expect to see IBM and its close partners showing up in a lot of new places ... living rooms, cars, planes, tanks, missiles ... and in new ways ... consulting, compositing, architectural methods, tools, and systems development, libraries of solutions.
This group of teams approach should foster meritocracies and agility. Members of the team will come and go based on the betterment and survival of the group. More importantly, the teams approach should make heterogeneity an asset -- not a liability -- and that's what SOAs are all about. The ecology approach also gives open source code a strong shot at being involved with the maturation of SOA from the get-go.
Yet almost everyone I speak to worries that talent may be the largest inhibitor to the advancement of SOAs in enterprises. As IBM executives described at the recent IBM Innovate event, a lot of "T" people are needed, whereby the horizontal bar represents wide business knowledge about the industry and niche that the SOA supports, along with a deep vertical bar representing technical acumen and implementation achievement. IBM is taking steps to help foster the emergence of more SOA "T" people, and they are hiring them all over the world as fast as they can.
Users can also view monitors that show Internet usage worldwide by interest area: retail, music, and news. This comes from data that is assembled by Akamai from its own Web monitoring. Another link to "Visualize Akamai" shows active streams, HTTP hits per second, and visitors per minute.
Mainsoft is offering a pragmatic approach to gaining a wide choice of deployment environments, including C/C++. The approach helps open C# developers to Java, and vice versa. It extends the utility of Visual Studio. And if provides flexibility in both runtime and design time. There's a portals-specific benefit too in that developers can attach back to portals in many environments: mainframes, Unix, Linux, and Windows.
Microsoft teams with Xandros as it faces a potentially wider open source software protection under GPLv3
Another commonality between the Xandros and Novell deals is the smell of real money. Novell as a public company we know has been under pressure. Microsoft came a callin' with a large stash of cash. We don't know the details of what will make Xandros a preferred Linux Server and Desktop Provider and a member of the Microsoft Interop Vendor Alliance. I'll be it wasn't peanuts, and Xandros probably really needed the money.