Category: Widgets
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
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?
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 »
April 17th, 2008
Web 2.0 success stories driving WOA and informing SOA
The striking contrast between the stories that we’ve been hearing lately about the slow going of SOA initiatives in the enterprise and the vibrant and rapidly growing ecosystems similar to them on the consumer Web has been generating a lot of debate and discussion in the enterprise IT community recently. This discussion was brought into sharp relief when ZDNet colleague Joe McKendrick recently reported on Burton Group’s Anne Manes stating that it “has become clear to me that SOA is not working in most organizations“, based on a wide ranging study they performed.
It’s become clear that the SOA world will have to change some basic assumptions.This is just one data point of many recently showing the continued shortfalls we’ve experienced in trying to get our enterprise systems to work together in the ways that we would like. Organizations clearly want to leverage high levels of interoperability to seize new business opportunities, innovate on top of existing assets, and properly leverage the extensive landscape of software, data, and infrastructure that most organizations have accumulated in large quantities over the years. But we are still having a great deal of difficulty doing so and SOA investments are just not reaping the types of return on investments that most businesses would like to have.
Looking for answers on how to improve SOA
This has driven a search for new models since there’s little question that the core ideas behind SOA seem to be the right ones. Rather, it’s been how we’ve gone about designing and implementing SOAs that appears to be at the crux of the issue. As we look at the most successful examples of SOA actually working, we keep being drawn back to the Web itself, with companies such as Amazon and their highly successful Web Services Division (with hundreds of thousands of business consumers of their global SOA), Google and its numerous and varied open Web APIs from Google Maps to Google Data, eBay and billions of dollars in listings it generates through its public SOA, or the rise of applications like Twitter (which gets 10 times the use through its APIs than from its user inteface) and applications that are primarily used via their SOA presence. Then there is the increasingly widespread adoption by millions of users of a sort of “visual SOA” with Web widgets and gadgets as well the rapidly growing story of software mashups, aka composite applications in the SOA world. There are many more SOA-ish success stories like this on the Web, but few in the enterprise.
John Musser’s ProgrammableWeb remains the best directory for finding all the APIs that Web companies have contributed to the Global SOA. Over 700 APIs are listed currently.
So if so-called Web 2.0 companies — which value participation almost above all else, both from consumers and organizations that want to integrate them into their offerings — are seeing highly desirable levels of adoption and significant ROI, how can this help understand how to improve our efforts in the enterprise? Most new Web 2.0 applications start out life with an API since getting connected to partners that will help you grow and innovate is a well-known essential for success online today. Despite years of SOA, we still don’t focus on consumption and openness as fundamentally essential characteristics to building an internal partner ecosystem that have beat a path to your door to use the services you are offering to them to build upon.
One big issue, as I’ve written about in the past, is
March 20th, 2008
Standards support for mashups emerge
The announcement earlier this week that IBM has put together an open approach for making user data secure inside of Web mashups, known as SMash, was the most recent step in an unfolding story about the way the industry is trying to bring structure and order to the rapidly growing and frequently unruly world of Web mashups.
As I’ve covered here in the past, mashups have enormous potential to allow more rapid and much less expensive development of online applications by emphasizing assembly over development, economies of scale by enabling high levels of reuse, and the consequent ability to rapidly get software solutions with the right data in the right place at the right time.
However, all is not rosy in the mashup space as I wrote last fall; there are significant challenges remaining before end-user or enterprise mashups can become a widespread reality despite the numerous offerings that exist today. Since then, I’ve only have one major new item to add to the list of adoption issues, namely that fact that most leading mashup solutions don’t provide a good enough SaaS delivery model. Consequently Yahoo! Pipes remains the best example of a mashup tool that has the requisite low barrier for use for widespread adoption, despite far more sophisticated and capable brethren from the likes of JackBe, Serena, and soon, Lotus, the latter which appears to be repackaging everything it learned with the impressive QEDWiki into an enterprise-class product.
Fortunately, good news is on the horizon for many of the issues I raised last year. It now appears that the mashup industry is heading in a direction which may make the space much more viable indeed over the next year. For example, two my biggest concerns, both non-starters for organizations that want to adopt a mashup model (21% of all organizations reported that they were interested last year), was 1) the lack of serious security and identity support and 2) not having a common standards for the assembly of Web parts such as widgets, gadgets, and other Web applications. Without knowing how to secure mashups, safely handle sensitive user and business data, or know where to make infrastructure and tooling bets, most organizations were likely to sit on the fence and wait until these risks were addressed.
IBM’s announcement this week about SMash was just one of many solutions now being offered resolve these two issues not only in the mashup space, but across the Web industry, as our personal and professional data gets more and more federated across the Internet and within our organizations. Efforts in this area include range from Google’s OpenSocial initiative to the push for adoption of DataPortability.org’s and OpenFriendFormat’s support which are all improving the world of data safety, security, and mobility in the mashup world as well.
But the most comprehensive and detailed plan for bringing standard approaches and techniques to mashups has to be OpenSAM, which leverages many existing standards such as WebDAV, openid, LDAP, and also subscribes to DataPortability.org’s standards to create a consistent and well-organized design and interaction model for offering complex, heterogeneous mashups to both the consumer and business community. Even more importantly, they cite a good number of companies already offering Web applications that support OpenSAM. The OpenSAM vision is broad and focused across the usage spectrum and the OpenSAM folks say that “once OpenSAM is added to an application, it can immediately join mashups with all other OpenSAM applications.”
While there is still a lot to sort out and the mishmash of standards can seem Read the rest of this entry »
January 3rd, 2008
12 predictions for Enterprise Web 2.0 in 2008
The worlds of SOA, SaaS, and Web 2.0 have been swirling around each other for a couple of years now and in 2008 we’ll finally see these gel into a practical, modern vision of next generation enterprises. And a variety of forces are coming together to make 2008 the year that enterprises refit themselves for the 21st century.
The driving forces for change this year will be the aging of existing IT systems, the rise of up-and-coming new approaches such as highly capable new Web-based applications, mashups, collective intelligence powered business software, Web-oriented architectures, and last but certainly not least, social software. These are providing the raw materials to use upon the freshly cleared canvases many organizations are readying for themselves as many organizations begin to retool and upgrade. Even the IT foundations we’ve come to get so used to, such as the operating systems we’ve used for years, have recently evolved and not always in the direction we’re going. If nothing else, the ever-advancing computing environments of the workplace and the Web are encouraging us to move to newer and better models out of sheer momentum.
But the changes we’ll see happening in our organizations won’t just be ones that are imposed by necessity, many of them will be driven from the bottom up as we see more and more grassroots IT solutions sprouting up from the trenches of Web-savvy workers, while many existing initiatives, including traditional SOA efforts, intranets and portals, CRM, decision management, and many others get recast and sometimes entirely reinvented using the lessons we’ve learned from the Web 2.0 era over the last two years, with the leading factors being the large scale shift of control to users, lightweight new application types proven in efficacy and scale on the Web, and social computing with Web technologies.
1. SOA finally goes pragmatic, Web-oriented, and lightweight. We’ve heard this prediction before but in 2008 it will be one of the items front and center for IT departments for a variety of reasons. Many of the ponderous, heavyweight SOA initiatives still in existence will finally refactor their design principles and then their architectures to be much more lightweight and RESTful. The classic SOA principles will still apply but changes in how they are realized inside organizations will just reach the tipping point in 2008. One key driver is that organizations are increasingly tired of waiting for ROI on their SOA investments and the demand for change is pushing IT leaders to search for new, more effective approaches. Web-orientation has enabled SOA on the greater Web on a vast scale and gained credence for a critical mass of the SOA community.
Read about ongoing story of Web 2.0 and SOA convergence, which will be well under way by the end of 2008.
The bottom line: If a Web service/open API can’t be consumed in the browser, it will find itself relegated to the deep end of the back office, if not retired outright. That’s not to say that the infrastructure for SOAs is getting simplier or that browser consumption is the ultimate litmus test, it’s not. And as we’ll see below, high velocity, large scale governance will be required to get any use out of these new highly distributable models for projecting content and functionality to any point in the enterprise.
Pervasive syndication for enterprise data, particularly with ATOM and sometimes two way, will also be a bright spot this year but will remain a largely emerging story until 2009.
2. Enterprise search will remain broken or highly limited in most organizations. I’ve covered previously the many reasons why search can’t work in the typical enterprise without enormous effort and consequently this won’t be fixed for most organizations this year. However, good enterprise search is necessary to leverage the fast growing and woefully under-leveraged information warehoused in the vast acreages of most enterprise data centers. Workers are still left with literally no choice but to pull their information from the Web or sequentially rummage through various silos to piece together what they need instead of putting a few keywords in an enterprise search engine and scanning the results. The unfortunate news: The penetration of local search engines into enterprise data will only improve a handful of percentage points this year.
3. Security will become a major concern as Web 2.0 apps and SaaS make the edge of enterprises increasingly porous. In 2008 users will self-provision themselves with consumer Web applications across the firewall, more and more business information will be found out in the open in enterprise wikis, workers will spend more time in public social networking sites, and the very pliability of mashup-based applications will make it unclear where data comes from and where it’s going. This will make security around next generation platforms become a Read the rest of this entry »
December 27th, 2007
The top Enterprise Web 2.0 stories of 2007
Over the last year, we have witnessed the continuation of the steady movement of the mostly consumer-driven Web 2.0 phenomenon into the workplace that began as a trickle in 2006. Blogs, wikis, social bookmarking, social networking, end-user mashups, and even prediction markets saw their largest entry yet into businesses and institutions around the world. The platform wars may start to return in 2008 as Web 2.0 ideas taught companies how to turn an open platform into competitive advantage.The more technical side of Web 2.0 also began to see maturity as businesses started to rethink their service-oriented architectures to be more Web-like and the rich Internet application industry added many major new building blocks and platforms that push the envelope in terms of the kinds of interactive experiences the Web is able to deliver.
Last year’s Enterprise Web 2.0 watch phrase of “consumerization of the enterprise” was clearly evident in workplaces large and small this year, yet we also saw significant new shifts in the way we look at online platforms of all kinds to communicate, collaborate, be more productive, and innovate. You may recall that the Web 2.0 mantra of 2004-2006 was often focused on emergent uses of networks to harness collective intelligence and provide next generation user experiences on the Web. And like each successive generation of innovation on the Web and elsewhere, most early attempts to capitalize on these powerful new ideas were relatively unsuccessful, though the success stories (which resulted in half of the top 8 sites in the world at the moment) resulted in both superior products for the Web community to use and useful new techniques we could use to improve our own results.
In 2007, we also witnessed a new pragmatism as the Web 2.0 hype began to die down, the success stories emerged, and the non-so-successful continued to inform the industry with the lessons needed to navigate the rocky shoals of product development on the Web today. We also began to see Enterprise 2.0 make real penetration in business as well as social networking finally get some corporate respect and validation as a functional business tool that can bring tangible benefits to the workplace.
Read here for a recap on what Web 2.0 and Enterprise 2.0 are generally defined as.
2007 was also a year of innovation in the mobile Web space. The iPhone proved that mobile Web devices were still capable of near quantum leaps in improvement and innovation, Twitter demonstrated what was possible in the realm of truly network-oriented social software on mobile devices, and Google dramatically improved their mobile Web applications with innovative capabilities throughout the year, particularly with Google Maps Mobile. However, while the iPhone isn’t quite ready for enterprise use yet (though it will likely get their soon), both Twitter and Google Maps Mobile have become poster children for mobile consumer apps that have had successful cross-over to the business world as enormously useful tools in day to day work.
But a contrarian might say 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
- The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... 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
- Finally, an easier way for Small and Mid-Sized Companies to Run Their Business Applications: IBM Smart Business IBM From the PC to the Internet to every piece of hardware and software in ... 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?
- Are the iPhone and social networks making the classic Web and intranet obsolete?
Top Rated
- Salesforce Chatter: Social operating systems emerge on the IT stage+5 votes
- Enterprise 2.0: What do we know today about moving our organizations into the 21st century?+3 votes
- Are the iPhone and social networks making the classic Web and intranet obsolete?+3 votes
- The cloud computing battleground takes shape. Will it be winner-take-all?+1 vote
Premier Vendor Content Whitepapers, webcasts & resources from our Power Center Sponsors
- 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 >>
- 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 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 >>
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
- The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... Download Now
- VMware Infrastructure: A Guide to Bottom-Line Benefits VMware Frustrated by the costs of maintain ever larger data centers?or building ... Download Now
SmartPlanet
- Thought-provoking progressive ideas on diverse topics that intersect with technology, business, and life, and matter to the world at large. Visit SmartPlanet
- More from IBM
-
- How to Drive Better Business Outcomes with Exceptional Web Experiences Download the eBook
- Driving Business Agility through SOA Connectivity & Integration Read the White Paper from IBM
- Linking Decisions and Information for Organizational Performance Read the Tom Davenport study
