Category: Small Pieces, Loosely Joined
September 24th, 2009
Creating a unified model for enterprise mashups
A unified mashup model can increase software quality, lower IT costs, and directly drive choice and innovation. I’ve written here over the years about software mashups; simple combinations of pieces of the Web that are rearranged into new useful forms. I’ve even called the approach a key to the future of software development. While mashups in the enterprise have been reasonably successful up until now — about a third of enterprises have them today — there have been challenges in enabling the same level of wide use and benefits that are currently evident on the open Web.
Fortunately, this may be about to change. Today marks the introduction of an effort by the new Open Mashup Alliance (OMA), a federation of interested parties in the mashup space that want to bring the benefits of standardization, consistency, interoperability, and a real marketplace to the world of enterprise mashups. The initial participants include a wide range of firms such as Adobe, CapGemini, HP, Intel, JackBe, Kapow, Programmable Web, Synteractive, and Xignite. Disclaimer: My company is also a founding member organization of the OMA. Note that anyone can become an OMA member, either as a company or a user and the principles of the organization are open and egalitarian.
Related: Joe McKendrick’s Enterprise mashup proponents start organizing.
What makes OMA especially interesting from my perspective is that it’s much more than a “high concept” strategic effort that will one day put forth specifications or technology that may or may not be useful to enterprises for creating mashups. Instead OMA sponsor JackBe, one of the world’s top enterprise mashups vendors, has generously contributed their existing and proven enterprise mashups model — known as the Enterprise Mashup Markup Language — along with a fully working reference implementation of an EMML runtime, as well as 50 working mashups.
Thus EMML exists fully today as one of the more mature enterprise mashup specifications available. It is robust, mature (it has been supporting production applications for several years), and now it is open for anyone to use via a Creative Commons license. And given JackBe’s technology roots in the Java community — their CTO is the respected John Crupi of Core J2EE patterns and Sun fame — it is free of proprietary technologies and formats. EMML also brings the leverage, speed, and power of domain-specific languages to the table as well.
The result is an open enterprise mashup specification and runtime model using familiar standards and/or community technologies such as XML, XPath, XQuery, SQL, JavaScript, and JRuby. Using the EMML reference guide, anyone can now create an EMML-compliant mashup runtime. This also means any EMML-based mashup is able to run inside any EMML-compliant runtime. The resulting mashups — because they are built with an open, interoperable specification — can now be published, shared, reused, and if applicable sold in a larger, standardized market. This creates the possibilities of a real enterprise mashup ecosystem and marketplace that wouldn’t happen of its own accord. The potential is not inconsiderable given that so far the enterprise mashups industry, lacking a consistent model (outside the browser itself, see below for further details) has been fragmented into a story of multiple competing vendors and technologies. This included IBM (Mashup Center), Serena (Mashup Composer), JackBe (Presto), and many others.
I’ve personally examined EMML and can attest that it’s a clean powerful design that includes potent capabilities such as declarative data transformation, advanced procedural logic, parallelism, meta-data and much more. That’s not to say more can’t or won’t be done to extend and evolve EMML but it’s a credible start to create a consistent model and runtime artifacts for the design and operation of enterprise mashups across all the vendors that support it. At its core, however, EMML and its runtime is essentially an enterprise-class version of Yahoo Pipes.
While it’s also true that today’s announcement will certainly not hurt JackBe as the top provider of EMML tools today, I also know — based on my conversations with them lately and over the years — that 1) they are a startup company that is volunteering the output of their hard work and is unlikely to vault to market domination on this basis alone and 2) that they believe this effort is one of the best practical ways to help enterprise mashups gain critical mass and that 3) the benefit to them is by improving the conditions of the enterprise mashups industry as a whole. At least that’s my perspective.
Ultimately, the OMA creates a standardized approach to enterprise mashups that creates an open and vibrant market for competing runtimes, mashups, and an array of important aftermarket services such as development/testing tools, management and administration appliances, governance frameworks, education, professional services, and so on. Creating an ecosystem like this is only possible when the mashup industry is focused on heading in the same general direction instead of competing over individual technologies (notably, this is one of the reasons the Web works so well).
Enough of the mashup development and runtime process is left open with EMML that there is also plenty of room for differentiation. While EMML will indeed level the playing field, vendors also have plenty of room around the edges to offer additional capabilities for EMML-based environments including visual designer tools/IDEs, modeling systems, administration consoles, portfolio management systems, and so on.
In the larger view, there has always been the tantalizing possibility for
September 6th, 2009
How the Web OS has begun to reshape IT and business
These days in the halls of IT departments around the world there is a growing realization that the next wave of outsourcing, things like cloud computing and crowdsourcing, are going to require responses that will forever change the trajectory of their current relationship with the business, or finally cause them to be relegated as a primarily administrative, keep-the-lights-on function.
IT is going to either have to get more strategic to the business or get out of the way. Businesses too must grow a Web DNA. The proximal cause of this seems to be the growing domination of the global network that surrounds all businesses today: The Web. If you’ve read my writings here since 2006 you largely know what’s happening: Today’s highly evolved Web has grown far beyond its original roots in content distribution and communication. It has become a fully fledged platform for media (TV, movies, music, newspapers, gaming, etc. have been strongly disrupted by the Web and now largely reside there) as well as more strategic pursuits. Probably most significantly is computing in all its many forms. This ranges from low-level services such as raw compute power and storage to social computing, semantics, and collective intelligence.
But the advent of a Web OS is certainly not just an IT story. It’s also — and really mostly — a business story. Those who are trying to track the so-called “big shifts” in the 21st century, thinkers like John Hagel, are attempting to pin down the specific changes taking place in the world today. John recently noted that “we are moving from a relatively stable business environment to one characterized by rapid rates of change with ever more disruptions generating increasing uncertainty and unpredictability“. In this way, routinely transforming instability and rapid change from a threat (which it is to most businesses today) into opportunity is a core skill that organizations increasingly must be able to cultivate.
That much of the pace of change today is driven by the modern world’s pervasive and instant global flows of knowledge is largely due to influence of the Web and its billions of two-way touchpoints with nearly a third of the world’s population (including practically all of the developed world). In addition to ultra fast feedback loops that drive real-time action/response scenarios in the marketplace, the Web has also become an incredibly efficient, inexpensive, and easy-to-use delivery system for just about anything that an interface can be wrapped around.
This has created a new form of leverage in terms of the ability to change and adapt by tapping rapidly and deeply into on-demand resources (be they computing, data, or even people and ideas) in virtually real-time. A recent article in the Wall Street Journal noted that because of modern technology, particularly the Web, business “initiatives that used to take months and megabucks to coordinate and launch can often be started in seconds for cents.” Clearly, this is a brave new world, even if it’s one that’s still happening more on the edge than in the core of businesses today.
WOA = Web-Oriented Architecture
CC/SRR = Creative Commons/Some Rights Reserved
AOP = Architectures of Participation
It’s a world where scarcity practically doesn’t exist and access to abundance is virtually free. It’s also true that the business models of the Web OS are only emerging as well. While monetization is prevalent for those consuming or participating in the Web OS, there is also a real and ongoing concern that it’s also the modern version of sharecropping. That traditional management approaches often don’t understand the nuances of these issues and aren’t designed to take advantage of this modern economic landscape, much less compete with a growing number of businesses that do, is a whole side story I’ll explore when I’m able. But it’s one in which the Web OS is increasingly forcing a serious reevaluation of modern business practices as well as the very notion of how an opportunity is defined, identified, and targeted.
What is the Web OS?
While there are multiple ways of looking at the Web as an operating system, from cloud environments that mimic a desktop operating system to sets of services packaged together and bundled as an individual product to companies, the largest — and the most significant — is the idea of an overarching and emergent Internet operating system. The data, services, and even communities of the Web are now programmatic and can be incorporated and remixed into any other business or product at will. The concept of a Web OS isn’t new. But its arrival on the scene in compelling form with serious impact to the enterprise is.
Over the last few years, as open APIs, social networking platforms, cloud computing, open identity services, sensor-driven databases (such as with GPS and OpenStreetMap), or even people (example: Amazon’s Mechanical Turk) have created open ecosystems in which anyone can participate, including business, both to contribute and to consume. The Web has become the ultimate outsourcing platform and one that is incredibly agile too, combined with economies of scale that are very hard to match. There are challenges too: Unpredictabilities and risks exist that must be dealt with both routinely and successfully.
But to perform well in this changing business environment organizations have to
August 11th, 2009
Pragmatic new models for enterprise architecture take shape
The best outcomes result naturally from self-organizing thought leaders in an organization that seek each other out and collaborate on shared solutions to their problems.Hear the words “enterprise architecture” and many people will turn away automatically. It’s not that they aren’t aware that technology drives so much of the modern world, they just think it doesn’t apply to what they do. The famous IT/business divide is too often kept this way because of mutual incomprehension, not-invented-here thinking, and apparently incompatible mindsets. However, this is beginning to change.
High technology continues to relentlessly pervade practically every aspect of today’s business world, prescribing what is potentially possible and often conferring enormous leverage when harnessed fully. But it has been the advent of the Web 2.0 era and its inexorable movement (some might even say infiltration) into the workplace that is making traditional IT — and the master planning version of it, enterprise architecture — an entirely new beast by popularizing simple, egalitarian tools and approaches that can be understood and applied more easily and quickly by a broad audience across most organizations.
Increasingly, in some IT departments and business units around the world, a closer new relationship is forming in which technology is deeply interwoven into continuous joint business processes of creation, change, and adaptation. Like so many grassroots tech culture movements, this one doesn’t yet have a formal name, but increasingly some are calling it emergent architecture.
The first seeds of this change began to be felt with advent of agile development processes a few years ago along with the subsequent rise of software mashups, and the popularity of user-distributable widgets, badges, and gadgets. These technology approaches combined with emerging business trends such as tacit interactions and pull-based systems driven from with bottom-up within organizations, particularly when co-existing with social computing and Enterprise 2.0.
The result: A new environment for creating technology-driven business solutions using different, more open communication channels with richer information and ground truth as well as significantly more adaptive technology elements often strongly influenced by the Web 2.0 world.
Meeting in the middle: Emergent Architecture
In recent years enterprise architecture has been moving from a discipline that provides top-down, a priori technology blueprints to the business side to one that articulates key, strategic possibilities and only the most critical high-level constraints (such as security standards) and then operates as a conductor, promoter, problem solver, and evangelist across the organization through the vehicle of a cohesive community to co-develop needed solutions.
When I wrote that most organizations were badly in need of a technology and software process “angioplasty” a few years ago, I highlighted the trends that will increasingly drive the agenda for new initiatives and projects when it comes to the strategic application of technology to business:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration (internal or external) over contract negotiation
- Responding to change over following a plan
This is more true than it’s ever been and has been contributing to a growing discontinuity in the way that enterprise architecture will be conducted in the future. Going away are overly formal procedures, detailed technology prescriptions, complex software frameworks, and dreaded compliance checks. Replacing them are highly collaborative, adaptive processes, technology opportunism, simple (frequently Web-oriented) technologies, and dynamic — even spontaneous responses — to organizational and marketplace needs.
Enterprise architects of the near future will still dispense clear guidance that carries the requirements of the entire organization with it, but it will be appropriately broad and EAs will actively help tailor it to local needs across the organization. Self-service IT will become much more common as workers are comfortable using today’s extremely easy-to-use, adaptive, and flexible tools, many of them using Web 2.0 ideas such as simple, open architectures and malleable pieces and parts, especially open APIs, and even new, open business models such as crowdsourcing and community-based involvement.
While organizations such as Gartner are just beginning to map this trend, there’s increasingly little doubt that the infamous chasm that often disconnects IT and business is being crossed in many quarters by business users unafraid of today’s populist technologies combined with IT practitioners that strongly desire to solve immediate and important business problems. That today’s collaborative and communication technologies in the workplace are much more open, social and collaborative than they were even a couple of years ago are likely to be
June 1st, 2009
Twitter on your intranet: 17 microblogging tools for business
Ultimately, if you want to use the right tool for the job, you’re probably going to need a specialized microblogging platform.So you’re bitten by the Twitter bug and want to bring the social messaging experience to work in order to connect with and share information conveniently amongst your colleagues. Perhaps you’ve even obtained permission to try out microblogging in trial form on your local intranet. You sit down and begin to see how you can adopt social messaging internally. It goes slowly at first…
As a Web-based consumer application, you quickly discover that while Twitter itself is a terrific environment, it isn’t very usable yet for businesses because of it lacks a variety of capabilities needed to fully work on the local intranet (details on this below). You wonder what other options exist to bring microblogging to the workplace in a business-friendly manner. Plenty, it turns out.
As we’ll see, choosing one carefully will be key to the long-term success of your experiment.
With the recent growth of Web 2.0 tools in the workplace (to about half of all organizations today), this scenario is becoming more common. The good news is that the broad success of Twitter over the last year has led to the introduction of a whole series of business-focused microblogging applications that bring many (though not yet all) of the necessary enterprise capabilities to the microblogging world.
What exactly is microblogging?
Read the rest of this entry »
May 30th, 2009
The enterprise implications of Google Wave
Google has launched many communication services since its inception yet none of these have had such obvious business utility or attempted to reinvent the collaborative process from the ground-up.Google announced their forthcoming service known as Wave this week to widespread coverage in both the press and blogosphere.
Created by many of the same team members that developed the highly successful Google Maps, the preview of the service itself on Thursday was quite compelling, resulting in a rare standing ovation at a tech conference according to ZDNet’s own Sam Diaz. Its egalitarian and federation-friendly design is intended to create an entire open ecosystem for communication and collaboration that Google is not-so-modestly touting as the reinvention of digital interaction circa 2009.
This is clearly a tall order, but the Internet leader provides plenty of substance to back up this vision despite growing evidence that individual companies may be losing the capacity to drive the agenda for the world when it comes to establishing successful new Internet standards and technologies. While the ultimate destiny of Wave itself is far from clear, it’s both intriguing and open enough that it will likely emerge on the radar of businesses large and small when it becomes widely available later in the year.
Wave’s relevance to the enterprise might seem premature with so many of the early and current Web 2.0 applications (blogs, wikis, social networks, Twitter-style social messaging, mashups, etc.) still — often arduously — making their way into the workplace years after their inception. Though we seem to finally be hitting a tipping point with 2.0 tools at work, Wave itself seems credible enough to get on our watchlists, at least to understand the implications.
The real question is whether there are really such significant gaps in the current state of Web-based communication that we need something new like Wave. With Google’s tendency to emphasize the consumer world first and the enterprise later, it’s also valid to ask if Wave will really have much impact on businesses. Interestingly, you might be surprised at some of the answers, so let’s take a look.
Wave: A communication and collaboration mashup
Google Wave itself consists of a dynamic mix of conversation models and highly interactive document creation via the browser. Using simple, open Web technologies (Google makes much of the fact that most of Google Wave is a open set of formats and architectures that is jointly developed with the Web community) Wave combines many of the key features of e-mail, instant messaging, media sharing, and social networking into a seamless experience and data set that are eponymously known as waves. All of this is opened up to developers via the Google Wave API.
The demonstration at the introduction of Google Wave (link below) showed how users can interact in real-time, collaboratively creating structured conversations that contain rich media, instant notifications, simultaneous user editing of the conversation, and live integration with server-side resources such as spell-checking and language translation. Most interestingly, while waves are relatively self-contained and use their own types of servers and data formats, they are easy to embed elsewhere or to build extensions for, enabling virtually infinite options for distribution over the Web or within the firewall, as well as rapid integration with existing applications and data. In fact, a wave is almost a form of social glue between people and the information they care about. And as we’ll see, this has implications for the enterprise world, not only with SOA but also with social communication in general as well as Enterprise 2.0 specifically.
See Waves in action: Watch the introduction keynote at Google I/O on Thursday.
What Google has done with the Wave protocol is essentially create a new kind of social media format that is distinctively different from blogs, wikis, activity streams, RSS, or most familiar online communication models except possibly IM. Both blogs and wikis were created in the era of page-oriented Web applications and haven’t changed much since. In contrast, Google Wave is designed for real-time participation and editing of shared conversations and documents and is more akin to the simultaneous multiuser experience of Google Docs than with traditional blogs and wiki editing. Though Google is sometimes criticized for missing the social aspect of the Web, that is patently not the case with waves, which are fundamentally social in nature. Participants can be added in real-time, new conversations forked off (via private replies), social media sharing is assumed to be the norm, and connection with a user’s contextual server-side data is also a core feature including location, search, and more.
The result is stored in a persistent document known as a wave, access to which can be embedded anywhere that HTML can be embedded, whether that’s a Web page or an enterprise portal. Users can then discover and interact with the wave, joining the conversation, adding more information, etc. Google has also leveraged its investments in Google Gadgets and OpenSocial, two key technologies for spreading online services beyond the original boundaries of the sites they came from. All in all, Google Wave is a smart and well-constructed bundle of collaborative capabilities with many of the modern sensibilities we’ve come to expect in the Web 2.0 era including an acutely social nature, rapid interaction, and community-based technology.
As the original announcement post explained, to fully understand Google Wave, one should appreciate the separation of concerns between the product Google is offering and the protocols and technologies behind it, which are open to the Web community:
Google Wave has three layers: the product, the platform, and the protocol:
- The Google Wave product (available as a developer preview) is the web application people will use to access and edit waves. It’s an HTML 5 app, built on Google Web Toolkit. It includes a rich text editor and other functions like desktop drag-and-drop (which, for example, lets you drag a set of photos right into a wave).
- Google Wave can also be considered a platform with a rich set of open APIs that allow developers to embed waves in other web services, and to build new extensions that work inside waves.
- The Google Wave protocol is the underlying format for storing and the means of sharing waves, and includes the “live” concurrency control, which allows edits to be reflected instantly across users and services. The protocol is designed for open federation, such that anyone’s Wave services can interoperate with each other and with the Google Wave service. To encourage adoption of the protocol, we intend to open source the code behind Google Wave.
The key here is that Google is expecting many more front-ends for creating and editing waves, depending on the individual requirements of various entities. Google Wave is their own front-end application for doing so and using HTML 5 in their wave client shows they are planning more for
November 4th, 2008
Open APIs reach new high water mark as the Web evolves
Late last week an important milestone for the Internet was quietly reached as the number of available open Web APIs crossed the 1,000 mark, according to the popular API tracking service, Programmable Web.
We are nearing the time when opening our supply chains across the Web isn’t just a good idea, it will be essential for competitive survival. While still seemingly small in number compared to the number of traditional Web sites that exist, open APIs have become an increasingly vital story for Web startups and traditional firms alike to cost effectively partnership, expand the reach of their products (and especially their data), and drive their network effect deeply across the Web.
It’s now almost uncommon to see a new Web product that doesn’t sport a shiny new API so that other online products can integrate the pieces they like into new experiences and offerings. In short, APIs allow a Web application or online business to have thousands of points of presence in other products, instead of just one.
Though APIs were pioneered by many of the original, successful firms on the Web including eBay and Amazon, which can both cite considerable returns for their efforts, it’s only been in the last couple of years that APIs have been taken seriously in a widespread way by the Web community and have become a new competency area.
In my discussions with many companies, one of the biggest obstacles to adopting APIs is a lack of understanding of what a non-visual Web presence looks like and how to build a business model around it. Business leaders are much more likely to understand investment in a traditional Web site, which they are familiar with and understand somewhat, than in an online software development kit, which is more developer-centric and which they are much less likely to fully appreciate, even though APIs can often have more strategic value than a Web site.
The good news is that emerging case studies and the impressive numbers from Amazon earlier this year are showing the the way and there has been a noticeable change in attitude and uptick in interest since cloud computing became such a big topic over the summer.
Yesterday, Programmable Web’s John Musser summarized some of the more interesting findings
September 6th, 2008
The WOA story emerges as better outcomes sought for SOA
Over the summer the enterprise IT blogosphere was swept up in a conversation around the concepts that many are calling Web-Oriented Architecture, or WOA. A different way to think about service-oriented architecture, WOA extolls a different but related set of technologies, in particular how to apply them in specific ways to connect our systems together into the solutions we need to take on our daily business challenges. WOA offers the exciting and fast-growth promise of the Web 2.0 world, while SOA has been seen as struggling and encountering low engagement in most organizations.
For those just joining the conversation, SOA is the most common set of top-level organizing principles and technologies that enterprises use to organize and connect their IT systems. However, SOA is increasingly in the firing line for less-than-stellar results and lack of business alignment. Few promising solutions for this have emerged lately, with the increasingly notable exception of WOA. WOA describes a compelling new focus that can address many existing SOA issues, but is sometimes at odds with traditional IT and business thinking.
Along with different technology emphasis, WOA offers a compelling new perspective on service uptake and consumption and offers potent ways of thinking about business models that can directly drive innovation and growth. Even better, we can now point to existing WOA success stories, albeit most of them in the online world. In short, SOA (of which WOA is a part) hasn’t looked this interesting in years. But like most new ideas, it inevitably faces challenges from the old guard.
For its own part, far from being a boring, back-office story about plumbing and infrastructure, SOA has actually seen better results than most of the enterprise architecture models that came before it. However, these returns have been fairly lackluster compared to what most business were actually looking for and what SOA practitioners wanted and were actively trying to achieve, certainly when any measurements of the ROI were taken. My detailed WOA overview last April tells the story: The Burton Group ultimately concluded earlier this year that “that SOA is not working in most organizations” based on extensive conversations with clients.
I’ve covered this territory a number of times in the past, most notably with an in-depth exploration of What is WOA?, but the story remains the same: WOA is being driven by the widespread success that lightweight Web services — and particularly their use in open APIs — are having on the open Web. The broad lesson that has been dawning on the enterprise architecture world this year is that this is what’s actually working in terms of what SOA has been trying to accomplish, but with a uniquely different approach.
Explore several WOA success stories and how they are driving SOA.
The tide seems to be turning in terms of the industry’s perspective of WOA as well. Respected SOA expert David Linthicum recently asked “SOA out, WOA in?” and seemed to think it was, noting it will take a long time, like SOA did, to make inroads in the enterprise despite its widespread adoption on the Internet. ZDNet’s own Joe McKendrick recently noted that “WOA wins hands-down over SOA in popularity contest” and Dave Rosenberg recently discussed WOA on CNET and took it as a forgone conclusion. And this is a key point: Many organizations I talk to are already using some WOA to some degree on the ground today, it’s just not being promoted like traditional SOA is, thereby missing the benefit of the support, documentation, guidance, management, and infrastructure/tools support needed to fully flourish.
We have started to see traditional organizations begin to offer WOA-friendly services to the world at large. For example, the World Bank recently opened its Web API to developers using the increasingly popular Mashery service, which allows an organization to outsource their WOA. Of course, WOA can be used solely inside the firewall but some of the most interesting scenarios involve integration with business partners, on demand in a very agile, lightweight fashion.
And in the end, this is the challenge. The use of WOA on the technology side is only interesting if there is support for the business for the scenarios it encourages. You could convert all your Web services from SOAP or REST and be fully ready for the resulting stream of consumer and enterprise mashups, API customers, and hundreds of new business partners, but not if you’ve not redesigned your business a bit. This is also one key reason WOA isn’t synonymous with REST. WOA is architecture, both technical and business, while REST is a style building WOA services. The implications of WOA also go beyond REST to include other Web-oriented scenarios such as widgets, browser-based interfaces, and so on.
WOA entails both technology and business change
Unfortunately, many businesses have not yet absorbed the lessons of the Web 2.0 era and still look at the Web simply as a way to deliver Web pages. This limited view and understanding of the Web’s potential means that most organizations do not have it on the radar to link themselves together in the enterprise-wide and Web-wide ecosystems of creation and integration that WOA can enable. SOA has always been about connecting systems and people together and — at long last — we have a clear path to potentially wonderful outcomes in terms of unintended uses. This includes the ability to access business opportunities inside of time windows which would previously have been unattainable with our traditional, heavyweight SOA models. But only if we truly change the way we think about how to leverage the network.
One last thing, it’s important to remember that no small system can sustain contact with a large system for very long without being fundamentally changed by it. This is what is happening with businesses (the small system, no matter how large) and the Web today (the big system.) The intrinsic nature of the Web is driving major changes in how we create network-based products and services and is inexorably turning us into Web-oriented businesses. Businesses that want to be successful on this network without understanding its fundamental nature and capabilities are only delaying the time it takes to reach the full potential the Web offers.
In this way, WOA often describes network business models (such as open Web APIs) that often seem very foreign to non-Internet businesses but are powerfully aligned with the way that the Web works. These models are almost certainly essential to be successful and flourish in the modern competitive landscape on our networks today. In this way, too many organizations will ignore adding a WOA aspect to their SOA work until it’s too late and the ability to generate strong network effects in their industry is greatly reduced.
WOA is just one of a set of transformative new distribution models for network-based systems.
So how do organizations start down this route to investigate the WOA way of doing SOA and seeing if it works for them?
Like many aspects of Web 2.0, WOA is not complex or overly expensive, it’s a way of thinking about interacting over the network and all the classic SOA principles still apply, which just create and expose them differently.
- Learn about WOA. Study the technology (HTTP, REST, syndication, open Web APIs, widgets, metadata documentation, Ajax, mashups, JSON, etc.), as well as the business and implementation side, including partner ecosystems, developer support sites, monetization, and chargebacks.
- Adapt WOA to your organization. Every organization will have a landscape of existing SOA approaches and technologies that WOA approaches will need to be added to. Furthermore, WOA does little good unless you’re willing to use it for what it does well: Provide the fuel for RIA-powered portal applications, enterprise mashups, your public APIs, and so on. Begun working through how WOA security will work in your organization (inline or through HTTPS, for example) and other key starter issues that are (hopefully) already described in your SOA governance documents.
- Conduct a pilot. Validate the items in #2 with a small pilot. Select a mashup platform that works well for your organization and try it out. WOA enables SOA to be used in a much more agile, open, and effective manner, with the right tools involved but only in an environment that supports it all the way through the “stack” from browser, server, database, development tools, and management infrastructure.
What are your thoughts on WOA? Will this finally be where the rubber meets the road for many SOAs?
August 1st, 2008
Enterprise cloud computing gathers steam
The days when organizations carefully cultivated vast data centers consisting of an endless sea of hardware and software are not over, at least not yet. However, the groundwork for their eventual transformation and downsizing is rapidly being laid in the form of something increasingly known as “cloud computing.” This network-based model for computing promises to move many traditional IT capability out to 3rd party services on the network.
The promise of cloud computing has captured the industry’s imagination this year for two big reasons. The first is the growing realization that cloud computing can successfully be used to strategically cut costs and drive innovation. And the second is that current offerings are getting very close to being ready for prime-time use in enterprise environments.
When Web behemoth Google officially entered the cloud computing arena back in April of this year, the space became a hot topic in IT circles almost overnight, despite the long history of availability from major vendors such as Amazon and Sun as well as a number of pioneering smaller vendors such as 3Tera and Egenera.
Other major IT players include IBM, Dell, HP, Intel, and Yahoo are all making serious investments in cloud computing research or major infrastructure Om Malik reported this week. ZDNet’s Mary Jo Foley is also tracking Microsoft’s movement in this space with project ‘Midori’.
Why was Google’s entry a signature moment in cloud computing? Most likely because it brought the necessary critical mass to an industry which was growing steadily but had yet to break out into the mainstream. Google has a well-known reputation for globally scalable applications that can reliably service millions of concurrent users while successfully controlling costs and efficiency in everything from power and bandwidth to storage and processing power. So when they claimed that anyone can now “build scalable web apps on top of Google’s infrastructure” it received considerable attention.
Cloudy IT: Increase efficiency while innovating
The twin challenges of driving the high costs of information technology down while providing innovative new solutions to improve the business are two forces that often come into direct opposition in the modern IT shop. Businesses must keep costs down to stay competitive while at the same time investing in new ideas that will offer compelling new products and services to those same customers.
These two objectives come into opposition since new spending (on things like R&D) is usually required to successfully innovate while at the same time the pressure is on to provide the same services for less than it cost last year. Companies have come to expect to reap the cost dividend from trends such as Moore’s Law, outsourcing, and year-over-year productivity improvements.
Interestingly, it’s at this very intersection of issues that cloud computing appears
May 15th, 2008
Mashups turn into an industry as offerings mature
There were a great many product announcements at Web 2.0 Expo in San Francisco last month, but it was the number of announcements around Web-based mashups in particular that received a large share of attendee and media attention. By my count there were at least nine significant announcements in this space, many around the business flavor of this emerging new type of ad hoc Web applications. These are often referred to as enterprise mashups and the growing number of offerings in this space run the gamut from Web widget assembly platforms for end-users to data-only swizzlers and remixing applications created specifically for IT professionals.
Penetration of mashups in the enterprise is just beginning as their benefits begin to be understood.One thing is now clear in this burgeoning new industry; that there is genuine interest in being a leading provider of enterprise mashup tools as organizations begin getting serious about applying them to make the development of Web-based business solutions faster, more commonplace, and less costly. One significant open question continues to be how long it will take for rapidly evolving mashup techniques to move into enterprises, which have been falling behind developments on the fast-pace of the consumer Web for a number of years now and are just now beginning to make inroads into some businesses.
And its a space that is expected to grow into a serious one in the next five years. A widely covered new report from Forrester estimates, however, that this space is expected to grow into a $700 million a year industry sector by 2013, or about 1% of the entire software industry, depending on how you define mashups and which types of tools are included.
For awareness and understanding of the fast-growing world of mashups are significant challenges as IT practitioners, business strategists, and software vendors attempt to grapple with what’s facing up to be the biggest challenge of all: The habits and expectations of the larger part of a generation of workers who don’t yet realize mashups are poised to change many things about the software landscape on the Web and in the workplace. Generational changes can be difficult for businesses to embrace successfully, and while evidence that mashups are remaking the business world are still very much emerging, they certainly hold the promise.
Figure 1: Mashup Tools and Platforms Circa 2008
However, the continued proliferation of high quality Web parts and open APIs, especially in the last couple of years, has offered compelling sourcing options for enterprise mashups is the making the expanding Global SOA compelling as local IT resources for building and improving business solutions. Combined with the consumer Web’s intensive focus on ease-of-use to gain adoption, and this has paved the road for low barrier, low cost effective assembly of software mashups instead of the time consuming and expensive design and coding of largely new applications. In this sense, mashups are probably the next major new application development model as well an increasingly popular approach for achieving better ROI with service-oriented architecture (SOA).
Mashup Standards Emerge: Read how a number of new mashup standards have appeared recently.
But while the life of the average Web developer has been greatly improved by the
April 22nd, 2008
Enterprise 2.0 industry matures as businesses grapple with its potential
Some of the big IT news over the weekend was the announcement that Forrester predicts that the Enterprise 2.0 space will be a $4.6 billion industry within 5 years. ZDNet’s Larry Dignan had the full breakdown yesterday on Forresters bullish outlook while Dennis Howlett immediately took umbrage with Forrester’s conception of the Enterprise 2.0 marketplace using a “loose definition and one that could be applied to any number of technology components from CRM through to supply chain management and pretty much anything between.”
Certainly that’s the challenge of pinning down something with a term that still doesn’t have industry consensus after two years, yet seems destined to be a vitally important space that our businesses are going to be moving to over the next few years. Enterprise 2.0 itself was originally defined by Harvard’s Andrew McAfee a couple of years ago in careful detail (early timeline) about something he called freeform, social, emergent software applications (such as blogs, wikis, but many others as well.) The enterprise software industry began carrying the banner ever since, applying Enterprise 2.0 to the next generation of countless marketplace offerings, often whether or not they were any of the things that seemed to make this new type of application unique and special.
Read The State of Enterprise 2.0, a thorough summary of this new software space.
The intent of creating this new term, however, was to capture a very significant change in the way that people use networked software, regardless of it was the genuine retooling of “big box” traditional IT software suites or the infiltration of subversive Web 2.0-style consumer applications across the firewall. Careful market segmentation for research tracking purposes and the debate over the inclusion of traditional, top-down IT systems into the definition of Enterprise 2.0 can be interesting exercises. But such efforts also miss the big picture and the long-term potential of this potentially potent new generation of enterprise software applications.
In my studies of Enterprise 2.0 adoption, there are two major methods by which these new applications take hold. The first is the traditional model where the IT department or some part of the business decides at a high level to adopt these new tools and begins the process of evaluation, acquisition, deployment, training and adoption. This is the traditional model that most IT large-scale software acquisitions still use today.
The other model is where individuals take it upon themselves to find the best solutions to a given problem at hand and solve them creatively and collaboratively at a grassroots level. This is becoming increasingly more common, particularly in organizations that are less strongly hierarchical and I’ve identified this story in many large organizations, from AOL’s stunningly rapid viral adoption of MediaWiki (the open source platform that runs Wikipedia) to the story of a large utility company getting ready to roll out Enterprise 2.0 only to find that the majority of departments had already adopted a solution on their own.
This second form of adoption is one of the hallmarks of this new model for using software to solve business problems and it speaks volumes to how different they are from the previous generation of applications. So it’s worth spending a little time understanding exactly why and how they are so different. To explain this, I often refer to Read the rest of this entry »
An internationally recognized enterprise architect and business strategist, Dion Hinchcliffe has been working for two decades with leading-edge methods to accelerate project schedules and raise the bar for software quality. You can follow Dion on Twitter.
See his full profile and disclosure of his industry affiliations.
Subscribe to Enterprise Web 2.0 via Email alerts or RSS.
SponsoredWhite Papers, Webcasts, and Downloads
- Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
- Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
- Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now
Recent Entries
- The cloud computing battleground takes shape. Will it be winner-take-all?
- Salesforce Chatter: Social operating systems emerge on the IT stage
- Enterprise 2.0: What do we know today about moving our organizations into the 21st century?
- Are the iPhone and social networks making the classic Web and intranet obsolete?
- Twenty-two power laws of the emerging social economy
Blogs From Our Sponsors
Most Popular Posts
- Salesforce Chatter: Social operating systems emerge on the IT stage
- Enterprise 2.0: What do we know today about moving our organizations into the 21st century?
Top Rated
Premier Vendor Content Whitepapers, webcasts & resources from our Power Center Sponsors
- The best support in the Linux business
-
If Linux is going to power your mission-critical applications, you'd better have the best support known to business. Novell was rated the top provider of Linux technical support.
- Learn more >>
- The more you simplify, the more you save
-
When you transition from your existing Red Hat environment to SUSE Linux Enterprise from Novell, you can recognize dramatic cost savings, perhaps as much 50%
- Learn more >>
- Learn more about tools to grow your business
-
The Business Essentials Guide provides you useful tools and templates to help grow your business and save you time with automated shipping solutions.
- Save time with the UPS Business Essentials Guide
- Keep Up With The Latest In Document Management with The DocuMentor.
-
Doc delivers the scoop on today's enterprise content management, printer maintenance, and all other issues related to document management. It's the DocuMentor Blog.
- Learn more >>
- New Online Dashboard for IT Leaders
-
Read about top issues IT decision-makers face every day, plus get cost-effective solutions to real-life IT problems.
- Learn more >>
- Microsoft Dynamics CRM Online - Free Six-Month Trial for Eligible Organizations
-
Microsoft Dynamics CRM Online provides fast online access, simple contact management and better sales performance for a low monthly cost - the best value on the market today.
- Learn more about the free, six-month trial offer>>
Archives
ZDNet Blogs
- All About Microsoft
- The Apple Core
- Between the Lines
- BriefingsDirect
- Collaboration 2.0
- Dev Connection
- Digital Cameras & Camcorders
- Ed Bott's Microsoft Report
- Emerging Tech
- Enterprise Web 2.0
- Forrester Research
- Googling Google
- GreenTech Pastures
- Hardware 2.0
- Home Theater
- iGeneration
- Irregular Enterprise
- IT Project Failures
- Laptops & Desktops
- Lawgarithms
- Linux and Open Source
- Managing L'unix
- The Mobile Gadgeteer
- On Sustainability
- Rational Rants
- The Semantic Web
- Service Oriented
- Smartphones and Cell Phones
- Social Business
- Social CRM: The Conversation
- Software & Services Safari
- Software as Services
- Storage Bits
- Team Think
- Tech Broiler
- Technology and the Global Supply Chain
- Tom Foremski: IMHO
- The ToyBox
- Virtually Speaking
- The Web Life
- ZDNet Education
- ZDNet Government
- ZDNet Healthcare
- Zero Day
White Papers, Webcasts, and Downloads
- Building the Virtualized Enterprise with VMware Iinfrastructure VMware VMware virtualization software has been adopted by over 120,000 enterprise ... Download Now
- Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now
- Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
Meet Doc
-
-
Here to help you with your Document Management Needs
- Check out Doc’s Blog on ZDNet
- Help your company, help the earth I want to share with you the Environmental Defense Fund Paper Calculator, which allows you to gauge your organization's environmental impact.
- Which is Greener: Paper or Digital? The Answer May Surprise You Anything we can do to reduce paper consumption is good. But what about the impact of digital waste?
-
Produced by
ZDNet and -
