Wednesday, April 2, 2008

ZapThink's Linthicum takes reins as CEO of data services provider StrikeIron

Service Oriented Architecture (SOA) consultant and author Dave Linthicum has taken over as CEO at data services provider StrikeIron, just six months after Linthicum sold his consulting firm to and became a managing partner of SOA analysis firm ZapThink.

On April 2, Linthicum was identified as CEO of StrikeIron in an article on SysCon.com, "RIA, SOA & Web 2.0 Mashups - Mash What?" StrikeIron is also conducting analyst briefings this week on Linthicum's new role as new CEO, though no news releases have apparently been issued.

Linthicum will continue as a ZapThink contributor and associate, said Ron Schmelzer, ZapThink managing partner and senior analyst. "Actually, it's a very positive thing happening.

"Technically, Dave Linthicum is still a ZapThink contributor and associate. We had negotiated something as part of our acquisition that would allow him to also serve as a CEO if an opportunity so presented itself. And one did. So, we're all still one big happy family,"said Schmelzer.

“I’m still a ZapThinker at heart, however I also have passion around what StrikeIron is doing and wanted to be a part of it,” said Linthicum. “I loved working with/at ZapThink. I will still be a contributor, adviser, and friend of ZapThink.”

Linthicum has offered his expertise on Enterprise Application Integration (EAI), SOA and Web 2.0 through speaking, consulting, advisory services, and prolific blogging and writing. In September, ZapThink acquired The Linthicum Group, making its founder a major partner in the SOA services firm.

Before forming Linthicum Group, he had been the CEO of BRIDGEWERX, former CTO of Mercator Software, and has held key technology management roles with a number of organizations including CTO of SAGA Software, Mobil Oil, EDS, AT&T, and Ernst and Young.

StrikeIron provides several on-demand web services offerings, mostly for data integration functions, as well as provides a marketplace for web services.

Tuesday, April 1, 2008

Apple makes headway on PC vs Mac front, but isn't that the old war?

The writing is clearly on the wall. The iPhone will grow into a significant enterprise end-point role, and OS X Macs will quickly advance beyond the now 20 percent share (estimated) of the total non-enterprise fat client compute device market. This is all but done.

Problem is that Apple is winning in the old war -- the PC vs the Mac, and the smartphone vs the mobile Internet device (MID) battles. The larger, more long-term opportunity has moved upward and outward into the realm of the services cloud. Becoming the funnel through which to acquire, access and pay for the cloud-spewing services is the new war. Client hardware isn't going to matter that much very soon, and will likely become free.

Just as Google Docs gains an offline capability, more of what will make people and workers productive will be what they get as pure services from cloud-based hosts. The next war is the cloud war, and the battles will be fought around software as a service, desktop as a service, integration as a service, infrastructure as a service, platform as a service, development as a service, content management as a service, and so on.

The new money will made through a combination of access subscriptions, direct payments for digital and media objects downloads, advertising, revenue sharing from online retail transactions, and B2B lead generation motifs.

Apple is in a good position to grab a portion of these revenues, but only a portion. Google is in a better position. And the Microsoft-Yahoo conglomeration may be in the very best position, but nothing is set in stone.

That means we should expect quite a bit of news out of Apple soon that has nothing to do with client-side hardware, and much more to do with the iTunes funnel and the .mac services cloud.

Microsoft seems to gets this. Because it does not have a client hardware business (mice and keyboards not withstanding) it can race to the next big thing on software, better than, say, Dell. Microsoft has all but given up on the the fat PC business for its future growth. Fat PC clients are a maintenance business now for Redmond.

As long as the packets make it down to the end point and get rendered, Microsoft can find new ways to grow, which are all about the cloud, integrated services, single sign on, virtualized CALs, and advertising. They call it software plus services, but it's all about the services and the dollars.

Microsoft may lose the installed Office business cash cow, but it can gain far more variety of services ... with ultimately a larger addressable market. Microsoft has figured out, thanks to Google, that the Internet business is bigger than the PC business. And these services may well represent a 50-year business trend line, instead of the fat client 20-year business that is now topping out.

Apple surely gets this too, and it's already engaged accordingly. So let me make some predictions. Apple will only have a handful more of meaningful product generations on client-side hardware. Yep, that's right, the iPhone and the Air are the beginning of the end, just because there's not too much more innovation needed down there in the hardware space. Please just add more flash memory capacity and build in the multi-protocol broadband network connectivity to the chip, and we can wrap it all up.

There's only about two to three more years left in the client hardware innovation business before the end-points go pure commodity, even with Apple's intellectual property. The hardware becomes a basic catcher's mitt for the packets, a single chipset that grabs the several important signals and processes them into a basic Web UI and supports the runtime, virtualized most likely. I, for one, don't want to see native iPhone apps; just use the browser and great UI.

But the software layer on top of the hardware, now that's a different story. And it's not a Windows domination segue guarantee, no sir. Too much baggage to support. Microsoft needs a standalone lightweight client story, and neither Vista nor CE is it. Microsoft needs to practically start from scratch on the client software of the future.

And so Apple needs to exploit this "window" of opportunity, and to take iTunes to a much larger role: The new lightweight operating system for the modern cloud services and commerce end-point. This new layer can very quickly emerge from iTunes-as-cash register for music version -- and grow into the everything else under the sun as a service (and cash register) layer.

And that's why Safari on Windows is a massively important campaign for Apple. For Apple to be a player in the cloud-based future, it must parley its iTunes hegemony into a Safari critical mass -- and that has to come at the expense of Internet Explorer and (sorry to say) Firefox.

Next, Apple will then need to munge together Safari and iTunes into a uber client layer for cloud computing-generated services reception and payments -- on mobile, PC, MID, anything that can catch the packets and support an iTunes browser. This is the funnel play, and Apple probably can do it better than anyone.

And so then comes the big question. Will Apple use this new software client model to make the services tie-in closed, open, or how open? Will Apple try and do on the Safari/iTunes client model what Microsoft has so far failed to with Windows? Will Google keep Apple open enough on all of this?

Microsoft, with the massive Yahoo audience it may soon own, will try and hold on to the client software chokepoint -- even as Apple makes a mad dash for it. This is the new war, and it has little to do with the difference between a Mac and a PC. It about both and how they access the clouds.

I suspect an Apple-Google partnership could outfox the Microsoft-Yahoo hairball, and that the Safari-iTunes-Android trifecta looks pretty interesting as the new client platform. What do you think?

Monday, March 31, 2008

WSO2 launches Web Services Framework for Spring 1.0

"Contract first" or "code first?" Spring developers now have a choice with WSO2's release of Web Services Framework (WSF) for Spring 1.0. The new WSF/Spring 1.0 integrates the Apache Axis2 /Java Web services engine into the Spring Framework, giving Spring users full control from within the Spring configuration model.

The existing SpringWebServices (SWS) within Spring supports Web services through the contract-first model, by which users start with XML schema and WSDL definitions of their service. WSF/Spring 1.0 adds code-first support, by which users can start with existing Spring beans and offer them as Web services with a simple Spring configuration.

Paul Freemantle, co-founder and VP of sales at WSO2, the open-source SOA company located in Mountain View, Calif., and Sri Lanka, explains why this new feature is important in his personal blog:

So how does this compare to Spring Web Services? Well, the first thing is that SWS is mainly about contract-first. And, while contract first is an excellent practice, there are times when it is not appropriate - for example, it may be simply too much effort for a simple first web service. WSF/Spring supports the POJO programming model simply and effectively, and generates the WSDL automatically from the beans you expose. (WSF/Spring does also expose contract-first). The second reason is simply that some users want to use Axis2. Axis2 is a very full featured and interoperable toolkit that does support some extra standards not yet available in SpringWS such as WS-SecureConversation, WS-Trust, WS-Policy and WS-ReliableMessaging. Axis2 also takes a very different approach to enabling these standards using the module approach rather than direct wiring of handlers.

WSF/Spring 1.0 is released under Apache License 2.0 and is based on the open source Apache Axis2/Java Web services engine. Key features include:
  • Support for the WS*- stack, including WS-Addressing, WS-Policy WS-Security, WS-SecurityPolicy, WS-ReliableMessaging, WS-Eventing, and SOAP Message Transmission Optimization Mechanism (MTOM).
  • Inversion of Control (IOC) container support enabling Spring services to be exposed through an IOC container, as well as support for editing the Axis2 booting configuration through the IOC container.
  • Automated WSDL generation via the Axis2/Java code generation tool.
  • Querying service support.
  • Method exclusion in Spring beans, allowing developers to have fine-grained control over which methods are exposed as Web service operations.
WSO2 has been making the news on a regular basis lately. In mid-January, it introduced its Web Services Framework for Ruby 1.0, building a bridge between Ruby-based applications and enterprise-class Web Services. Later in January it launched its Mashup Server 1.0, which combined JavaScript and Web services. [Disclosure: WSO2 has been a sponsor of BriefingsDirect podcasts.]

WSF/Spring 1.0 is available for download today, and carries no software licensing or subscription fees. Support is available from the WSO2 site.

Thursday, March 27, 2008

We know SOA depends on cultural shifts, but -- like the weather -- we still don't do much about it

Recent observations on SearchSOA.com on lack of meaningful SOA adoption suggest that the technologies and techniques have amounted to but a mere improvement on EAI. Some conveniently calling it EAI 2.0, but admit the effects are not yet wide nor deep.

We have yet to see SOA adoption lead to substantive transformation, surveys and primary research will no doubt indicate.

The acknowledgment that SOA requires top-down, bottom-up, organizational and behavioral, ie "cultural," change to proceed to its potential is well documented and debated. We have come back to this topic again and again, for example, on the BriefingsDirect SOA Insights Edition analyst-powered podcast series.

So let's recognize that a higher purpose is at work here, and that SOA is a subset -- not even a leading driver, perhaps -- of the end-game. Also augmenting and influencing the IT transformation journey in addition to SOA are several mega IT trends and shifts (in no particular order): SaaS, RIA/mashups, virtualization, cloud computing, open source adoption, ITIL adoption, business process outsourcing, applications modernization, data center consolidation, SAN adoption, BI, BPM, master data management, etc. etc. etc.

There are great new tools and effects that can make IT perform better. The tech folks obviously have their hands full with them, and are often expected to implement under the "do more for less" ongoing mandate, the unfortunate business-side takeaway from Moore's Law.

But these IT efficiencies are the means, not the ends. The end-game is business transformation. Contingent to and in coordination with that is IT transformation. The relationship between the two is intrinsic, interdependent and highly variable -- from enterprise to enterprise, IT department to IT department -- often an enigma in motion. While the IT trends deeply affect the trajectory of the IT-centric transformation, they to do necessarily have an understood or appreciable influence on the business transformation processes.

Frankly, it's all too complex, too unwieldy, too unmanageable -- this bridging of the "business side" with the "IT side." People and passions play a huge role, too. Agendas get crafted. Sides are taken. Leaders and followers emerge. Politics permeates the process, regardless of how well the IT performs. And then any means to meaningfully simplify the complexity (tactically or strategically) become themselves highly complex. And so on. And so on. Transformation remains a distant vision.

There remains therefore an ongoing, pernicious reinforcement gap between the change agents of IT, the change agents of business requirements, and the means to engender change in cultures, groups and individuals. In other words the politics of change in large, complex organizations remains a mystical, quizzical patchwork of leaps, lunges and stumbles.

Let's not necessarily blame SOA or IT, any more than we should blame the rain. SOA in of itself is not enough to overcome the many obstacles on the path to ongoing and effective business and cultural transformation.

And yet, companies do succeed. Profits are made. Solutions are crafted and delivered to markets. Buyers keep buying, and workers keep working. Productivity seems to emerge and proceed at a certain scale, at the right level of decentralization. They say our brains are constructed to work best in close groups of 8-10, and to seek cooperation in larger groups up to about 140. Family and village are the scales we've been designed for. People therefore naturally seem to gravitate back to the scale that works, and perhaps even subconsciously resist moving beyond the perceived scale (and perhaps natural order) that actually functions for them.

There's a fascinating new essay by Paul Graham, "You Weren't Meant to Have a Boss," that relates this to developers and software development, but there may be a larger lesson in it, too. IT is great and keeps getting better by leaps and bounds, but biology and evolution are destiny. IT needs to line up behind this fact, not seek to side-step it -- or worse, ignore it. It's not nice to fool mother nature, as the margarine commercial used to say.

Politics is the process by which groups of people make decisions. SOA's expected role and virtue is closely tied to politics. And the decisions being made by IT executives, by business management, and by the line of business implementors often have very little relationship, little in the way of interchange between the people and the processes in a natural order.

SOA's great promise is to help align people, process, and processing. But something remains in the way. SOA lacks a political context. It lacks power over the people, and so far the power of the people has not been much interested in embracing SOA. Why should they?

We in the industry have not answered this question: Why should the people promote SOA as a means for them to get their jobs done in the ways they know work best in real life. What's in it for the average bear? What are the incentives to SOA adoption for those carrying the load?

The politics of SOA needs to succeed if SOA is to succeed as a lynchpin of both IT and business transformation. When SOA's virtues are translated to real improvements to real people, we may see the myriad gears of adoption mesh.

There should be a good story here. I think SOA is part of the answer, not the problem. But looking to SOA to change cultures seems to be a moot expectation. Politics changes cultures, and cultures are reflected in politics.

When the business consumers of IT services demand SOA and its effects, then we'll see the real transformation.

Tuesday, March 25, 2008

Elastra emerges to make cloud computing more attainable for enterprises

Cloud computing as a concept has been gathering significant interest in the past months, but aside from developers, testers and startups, the ability to exploit the efficiencies and cost-benefits of cloud computing for average enterprises have remained hard to grasp.

Startup Elastra unveiled its approach today to making cloud computing more practical, introducing two markup languages -- one (ECML) that helps pull applications together to deploy to a cloud environment, and a second (EDML) to help define and organize the right cloud-based infrastructure to support those applications.

In general the Elastra approach provides onramps to compute clouds based on descriptive tools that help reduce complexity for IT departments. This should encourage experimentation and ultimately lead to ramp ups in the use of public clouds, as well as the build-out and use of home-grown, so-called private clouds. Less attention has been given of late to the promise of private clouds, which are really a natural extension of current datacenter consolidation, clustering, application modernization, ITIL and virtualization initiatives.

As virtualized software has become the primary layer over now-buried hardware that architects and engineers must deal with, we should expect more tools and "bridging" technologies like Elastra to emerge to help grease the skids for what can (and should?) be deployed in clouds. The software then becomes agile services that can be provisioned and consumed via innovative and highly efficient business models and use-based metering schemes.

I suppose we can coin this as "middleware for cloud computing," or maybe "APIs for cloud computing." In any event, let's hope these onramps become highly visual, automated and increasing based on widely accepted standards.

Because Elastra's approach allows applications to be deployed to public (like Amazon's EC2/S3) or private clouds (like the ones many enterprises are likely to build out as they virtualize datacenters), it aims to become a de facto standard for accessing cloud resources. Packaged under the Elastra Cloud Server, the database-driven product can help bring applications rapidly to a pay-as-you-use model. Enterprises may be able to provide more applications as services, charging internal consumers as a managed service provider.

I had a chance to sit down last week and discuss the arrival of ECML and EDMl with Kirill Sheynkman, president and CEO of Elastra. He was a major force behind integration and enterprise portal provider Plumtree Software, which was acquired by BEA in 2005. Indeed, there are a lot of former BEA folks under the hood at Elastra.

Sheynkman is obviously a fan of cloud-based infrastructures, and also has had experience on what it takes to practically define and introduce a new category to the enterprise IT mind. His vision for the cloud opportunity is compelling, but his feet seem firmly on the ground, with a strong sense of what will work in real-world use.

Part of Elastra's DNA is putting more data in the cloud, where it can be used assiduously to support apps, services and business processes. And once the data layer makes its way to the cloud (private, public or both), can the rest of the support infrastructure be far behind? We're already seeing a lot of talk around integration as a service, and infrastructure as a service. And we're also increasingly seeing tools and development as a service.

Once the IT support infrastructure is effectively abstracted to a cloud, with specific languages to manage and access those resources, then the move to Nick Carr's utility vision seems well under way. What remains is for the tools and architecture definitions to be readily described, communicated, and managed for the compelling economics of cloud-based support to take off.

I'm beginning to think the segue to the cloud could happen sooner than many think, and be very much a mainsteam enterprise endeavor after all.

Wednesday, March 19, 2008

SpringSource releases tool suite based on Eclipse Mylyn

SpringSource, the company behind the Spring Portfolio Java application platform, has announced its SpringSource Tool Suite, a Spring-specific developer tool set designed to reduce the complexity of enterprise Java development and maintenance.

Based on Eclipse Mylyn, SpringSource Tool Suite extends Mylyn's task focus, tool integration, and workflow streamlining to enterprise application development and is designed to relieve information overload for developers by identifying only the information relevant to the task at hand.

Targeted to both ends of the developer spectrum, the tool suite provides tool-guided assistance to newcomers to the Spring Framework, while providing seasoned experts with architecture review tools to ensure best practices and support tools for finding resolutions for incidents.

The tool suite builds on the success of Eclipse, Mylyn, and Spring IDE to simplify the large aggregation of tools used in complex applications.

While the SpringSource press releases glossed over many of the specifics of the tools suite, Charlie Babcock at Information Week did a little digging and found some nuggets:

Java developers frequently test their programs by running them and are notified of runtime errors, prompting them to search through thousands, or hundreds of thousands, of lines of code, to find the errors. With the SpringSource Tool Suite, they will be able to zero in on problematic code, with the relevant lines highlighted in a different color, said Christian Dupuis, SpringSource lead engineer on the SpringSource Tool Suite, in an interview. By mousing over the segment, the Tool Suite will consult a database of known problems and in some cases be able to recommend a solution.

In other news, SpringSource has joined the Eclipse Foundation and will assist in developing the Eclipse ecosystem.

Sybase releases iPhone enterprise email solution

Sybase has now released the iAnywhere solution for bringing enterprise emails to the Apple iPhone. We blogged on this just a few days ago.

Based on the reaction, Sybase will get a lot more evaluation for their mobile messaging solution, even though it's designed to work with most all mainstream smartphones.

And, my, oh, my, I just keep seeing more people with iPhones, just about everywhere I go this week in the Bay Area. I'm glad this is panning out as I expected a mere hour after the announcement of the iPhone's pending release.

Apple has finally found its toehold in the enterprise with iPhone. The only question is much of the rest of the Apple bandwagon gets dragged into the big business maw. I have to say, using Keynote to whip out a preso I'm giving this morning saved my butt. Trying to do it in Powerpoint would have made me miss the point.

Oh, and now Safari runs on Windows, faster than most, and comparable to FireFox 3.x.

Yep, despite the Microsoft-funded malarky from some quarters, Apple is pushing its envelope further than ever. Productivity wins after all?

Monday, March 17, 2008

EclipseCon debuts OSGi runtime offerings, common platform frees up developers from middleware drudgery

Tony Baer has a great rundown of the EclipseCon OSGI-based runtime Equinox news today. Extending the Eclipse community's unity to runtimes makes a ton of sense, given that developers can focus on the applications and business logic and become far less concerned with complex deployment issues. Write once, run anywhere?

Eclipse's component development plan, called CODA (Component Oriented Development and Assembly), hinges on Eclipse's Equinox, which is the foundation's OSGi-based runtime and a part of the new Eclipse Runtime project.

The best new benefits will come in the conjunction of the Eclipse tools and Equinox runtimes. For example, developers in a vertical industry niche can use the tools and runtimes together and via community synergies enjoy a "common platform for participation."

I've long been a complainer about the gulf between runtime and design time, with the clear need for better feedback between the two -- especially in the era of Agile and web services assembly. An Eclipse-Equinox ecology symmetry gets us on the way.

The arrival of OSGi-based runtimes also conjures up the ability to repackage middleware as OSGi bundles, sort of like the BEA microarchitectures, which would be most welcome in highly virtualized runtime stack environments. Are you going to need a full LAMP or Windows stack to support a service in an SOA? Why not build a SOA stack on top of Equinox? Check out Swordfish on this sort of thing.

I can see where the OSGi runtime stuff, open source ESB stuff and variety of SOA tools in general can come together in fruitful ways. Flexible custom stacks and SOA make great conceptual bedfellows. Optimized stacks on the fly?

There are also implications for the SaaS and cloud folks, whereby they can look to these flexible custom Equinox stacks to efficiently support their applications and services, be they in virtualized or traditional stacks. Custom build the apps from the ground up, for better performance, less waste, less integration headaches. Green, baby.

What's more, the whole mobile and MID space is a perfect target for OSGi runtime bundles, given that OSGi originated in the embedded space. Small, lightweight, and reliable -- works for me. Sprint is already an OSGi fan. I think we'll also see OSGi running closely with Android. And Android on the iPhone (someday) offers a very interesting future.

Who loses from a viral Equinox runtime community and uptake? Well, Microsoft and .NET offer similar values, but with less openness and choice. The Java community is entertaining some JSRs, numbers 291 and Sun's 277, that undergird new component models. Sun losing traction on 277 could mean a further loss of control over Java.

Winners could be IBM, because the Lotus Notes and associated groupware clients are already OSGi-based. Community development around Notes, et al -- nice fit, for sure. They ought to give all that Notes client stuff away under OSS licenses anyway, no?