inicio mail me! sindicaci;ón

Archive for Sponsored Post

The Donut and Terror

by Rob Paterson

I have been writing about how the “Donut” will replace the traditional organization.

Here is Kilkullen on how the “Donut” works in the Terror context:

donutcorelilkullen

I find it fascinating when I find that someone I don’t know has seen the same as I.


SOA and SaaS convergence points to new market demand for ‘integration-as-a-service’

by Dana Gardner

Read a full transcript of the discussion. Sponsor: Cape Clear Software.

Take SOA and SaaS to their natural maturation and adding more interoperability and integration into the online services mix becomes inevitable. When standardized services come from a variety of sources, then a variety of means to connect them makes more sense, too.

So when will we see the first signs of integration as a service?The answer, it turns out, is now.

As the use of Enterprise 2.0 mashups sweeps the IT industry, the concept of converging enterprise services has expanded to hosted munging of business applications and back-office functions.

Why not then extend SOA itself by embracing more integration services that help vendors, ISVs, and service providers bring more elements of business processes together, too?

The budding notion of “integration-as-a-service” allows enterprise business leaders to “shop around” for their services, regardless of hosting, and opens up the prospect for a thriving new ecology of services and integration models for mission-critical activities … not just for maps and widgets. The advancement to SOA for many companies may well be accelerated by more choices on means of on-demand connections, both inside and outside the organization’s own IT boundaries.

I recently conducted a sponsored BriefingsDirect podcast discussion with Annrai O’Toole, CEO of Cape Clear Software, on the eye-opening prospects for integration as a service. Early adopters are already outsourcing aspects of integration.

The implications are staggering: Business operators and entrepreneurs create and amend complex processes and workflows through a simple point and click interface that prompts integration that’s executed on someone else’s infrastructure. Pay by the use or general subscription. Retain control over data and ID management.

Here are some excerpts from the discussion:

A couple of factors are driving this. First, it’s the whole technology maturity thing. Six or seven years ago, the standards around Web services were in their infancy, and people didn’t have a lot of experience with them. Because they were young, unproven, untested, and lacking in key bits of functionality, people didn’t really want to go there. Technology is one element of it, but there are a few more important elements driving it as well.

One is a secular trend toward simplicity and flexibility. At some levels, this has been driven by teams through virtualization. Storage and processing power are being very quickly virtualized. Applications are being virtualized, with software-as-a-service, on demand. There is a long-term shift by customers, who are saying, “We don’t want to own complex infrastructure anymore. We’ve been there, and done that. We want something else.”

We had an RFP come in – and this isn’t all that unusual – from someone looking to do a big SOA initiative. It was – and I’m not joking — a 111-page RFP.

Customers look at the choices available to them, and say, “Do we want to do all this big SOA integration on our own by buying these complex things, or are we prepared to look at alternatives? And, do those alternatives have any reality?” They do, and many companies are shying away from these big, complex initiatives.

You can sit in a room with a bunch of executives, both from the business and IT segments and, say, “Hosted integration is a good idea,” and they’ll know that. We’ve got some proof points around it. Most notably, one of our marquee customers in the software-as-a-service base is Workday. The PeopleSoft founders got together to rebuild an ERP application, but this time on a hosted basis. Read the rest of this entry »

 
icon for podpress  BriefingsDirect podcast discussion with Annrai O'Toole, CEO of Cape Clear Software [41:15m]: Play Now | Play in Popup | Download (593)

WSO2 expands ESB market with Apache Synapse-based, open source SOA offering

by Dana Gardner

Read a full transcript of the discussion. Sponsor: WSO2

WSO2, Inc. has entered the open source SOA field with a slate of veterans from Web services specifications, application server design and lightweight framework development. The company’s latest offering to the market came June 11 with the arrival of WSO2 ESB 1.0, based on Apache Synapse and targeted at both developers who want to use enterprise service buses (ESBs) quickly, as well as operations architects seeking lightweight and high-performing components.

To help better understand and evaluate WSO2’s approach, I recently moderated a sponsored podcast with guests Ron Schmelzer, senior analyst at ZapThink, and Paul Fremantle, co-founder and vice president of technology at WSO2.

Here are some excerpts:

I’ve been impressed with the fact that SOA is creating early-on an environment, in which open-source products are, in a sense, defining feature sets and approaches. In the past, we saw commercial products establish niches and define infrastructure areas that then became areas that open-source products might pursue.

One of the things that makes SOA different from CRM, ERP, or even traditional enterprise-application integration is that SOA is architecture. It’s a style, an approach, or a methodology for building loosely coupled, composable services that meet the needs of the businesses. So it doesn’t really demand a particular technology stack. As a matter of fact, people can implement SOA using a very wide variety of technologies, which they probably already own.

One of the things you see again and again in the computer industry is that people get to a point where they layer technologies on top of each other, and then it just gets too heavyweight. The benefits of reusing that old stuff are outweighed by the disadvantages.

We were very involved in open standards and in writing and implementing the specifications, but many of those implementations were layered on top of the Java EE enterprise runtime. We found that there was a whole new middleware based on XML and self-describing messages based on simple HTTP communications that didn’t need the existing EJB/Servlet runtime — that didn’t need to have all those existing layers.

So our philosophy when founding the company was to look at stuff afresh, and to build things with the simplest, most-lightweight combination possible. We tried to target users’ requirements, rather than target an existing code base and legacy solution than we might have if we were working for a large company.

We need to cover not just the Java platform but also the C, Perl, and PHP — the full gamut of platforms. SOA is not just a Java story. It’s really a cross-platform, cross-technology standard approach.

What you used to see was that companies would put together a kind of magic package, which was intellectual property, plus support, plus training, plus everything. And somehow they’d value all of this at some astronomical figure. Read the rest of this entry »

 
icon for podpress  Learn more about the arrival of WSO2 ESB 1.0 [43:45m]: Play Now | Play in Popup | Download (538)

Has the long-expected wave of cyber crime/warfare finally appeared?

by Dana Gardner

Reports in The Economist, New York Times, and PC World point to a stunning lurch in the sophistication and reach of recent nefarious online attacks. And the initial sniff test pulls up a whiff of state or large-scale organization sponsorship and support of these events.

They may well be a bellwether of what to expect. These are likely not loosely aligned hackers, but outright strategic aggression designed to influence politics and the behaviors of nations and large corporations.

As many of these articles allude to, the attacks problem will not get any better until the basic architecture and governance of the Internet technologies themselves are addressed. Band-Aids on 1,000 cuts only propels the ongoing Spy vs. Spy gamesmanship — only the stakes are fast escalating.

And so with that I dust off a sponsored conversation I had last year with Akamai Technologies co-founder and chief scientist, Professor Tom Leighton. In it he pretty much predicts — nearly a year ago — what we’re now seeing. His prescriptions are not easy, but they increasingly seem necessary. Read the transcript, or listen to the podcast.

Disclosure: Akamai is a sponsor of BriefingsDirect B2B discussions on the Internet and society.

 
icon for podpress  Akamai's Leighton on cyber security [28:22m]: Play Now | Play in Popup | Download (1414)

UPS visibility solutions help businesses drive customer service via managed supply chains

by Dana Gardner

Read a full transcript of the discussion. Sponsor: UPS

Effective information-sharing across the distribution of goods — visibility into transportation supply chains and distribution networks — is a vital part of the information revolution and the knowledge economy.

Global and local players in the total distribution channel are constantly looking for reductions in cost, efficiency improvements, and slashed time to distribution — all of which can substantially reduce the total cost of an overall production and distribution activity, and heighten customer service and satisfaction.

UPS started with tracking on the Web in the early 1990s and today supports online tracking in 63 countries. UPS has extended basic services to cover broad supply chain visibility for shippers, receivers, importers, and exporters — both residential and commercial — through its traditional U.S. small package services, as well as via global UPS Freight, Air, and Ocean Freight Services.

I recently moderated a sponsored podcast that examines the market trends driving the need for greater supply chain technology and efficiency, as well as the visibility services UPS has in place. Joining me was Jim Rice, director of the Integrated Supply Chain Management Program at MIT; Stephanie Callaway, director of customer technology marketing at UPS; Frank Deen is the shipping manager at Rackmount Solutions, and John Schaffer, president of TrueWave.

Here are some excerpts:

… Companies and leaders [are] concerned … about continuity — business continuity. We saw that destructions like Hurricane Katrina and 9/11 caused a lot of companies to start recognizing that their supply chains are genuinely at risk.

A lot of vulnerabilities were always there, but weren’t very apparent or evident. So, there’s a fair amount of recognition about this vulnerability. Right now, there is some work going on in that some companies are planning to make their supply chains more resilient and trying to actively manage risks.

The companies are concerned with optimal supply chain design, and this takes in the aspect of outsourcing. How much outsourcing do we use? How much of that do we even think of putting offshore, trying to reduce cycle time, cost, and uncertainty in the system? That will ultimately enable them to be much more responsive to spikes and drops in demand.

Companies continue to squeeze their supply chain to lean it out, and make it more efficient and more effective. There are a lot of drivers in the industry right now that affect the price of sundry industries differently.

A lot of it comes down to having relationships with customers and suppliers. They would be open and free to share the information that ultimately will help both organizations to make better decisions, reduce uncertainty in the system, and take out some of the cost and uncertainty. That makes the system potentially much more efficient.

Some of these capabilities are becoming more readily available for large companies, and hopefully in the near term, to small- and medium-sized enterprises. The challenges aren’t simple, but I think there are some tools and processes emerging that are going to make this much more possible in the future, and therefore get us a little closer to that Nirvana of the synchronized supply chain.

Initially, when we started doing this, because we were shipping from so many locations, even though it was being shipped on our account, we would have to contact each one of those shipping points, each warehouse, each manufacturer to get tracking numbers to send to our customers. Of course, now we are able to have that information sent directly to the customer when the product ships. They get an email with that information.

Plus, on UPS Quantum View, we are able to pull up a report every day that shows everything that has been shipped out on our account, whether from our local warehouse or any of those other locations. We’re able to have that tracking number and see the exact progress of that package — when it was picked up, where it’s at currently, when it’s expected to be delivered, and the address that it’s expected to be delivered to. When a customer calls and asks a question about it, we are able to go to that and immediately give them an answer that provides a comfort level that we are keeping track of their merchandise that they are waiting to get.

We could get to the markets, but we couldn’t do in a way that allowed our customers to have visibility into the process. There’s a lot of uncertainty when you are shipping internationally. When you have visibility into the process from point A to point B, it really changes the dynamic quite a bit. One of the tools that Stephanie was discussing, Quantum View Manage, allows us to see if there are problems along the way. Then we can communicate with our customers in such a way that we can set the proper expectations.

Read a full transcript of the podcast. Sponsor: UPS

Listeners or readers of this podcast are invited to learn more about sponsored B2B podcasts.

 
icon for podpress  UPS provides greater supply chain technology and efficiency [37:36m]: Play Now | Play in Popup | Download (1327)

Open source projects increasingly empower SOA infrastructure definition and development

by Dana Gardner

Read a full transcript of the discussion. Sponsor: IONA Technologies.

Unlike earlier open source initiatives, which often trailed commercial development of crucial software infrastructure, today’s many community-based services oriented architecture (SOA) projects are early-on defining the means through which SOA can be realized.

Development of commercial and open source versions of essential SOA components are happening concurrently. Open source SOA projects are providing a unique opportunity for developers to get their hands dirty and learn a little bit about the field, as well as contribute back some of their ideas in a form that is very healthy for new technologies.

Many commercial vendors are creating large software infrastructure stacks that are designed to target their customers with things that they have supported in the past. But a lot of new technologies and methods are also popping up, from rich Internet applications using AJAX applications, to new ways of using master data services — all of which present a new set of challenges, and a new set of connectivity options — that community development is great at solving.

To explore why this is true and how open source will shape the future of SOA infrastructure, join Dan Kulp, principal engineer and community lead at IONA Technologies, and Debbie Moynihan, IONA’s director of open source programs, for a sponsored BriefingsDirect podcast discussion, hosted by me. IONA Technologies is taking an active role in several open source SOA initiatives, including the Apache incubation CXF enterprise service bus (ESB) framework project.

Here are some excerpts:

One of the goals of an open-source community is to bring new developers in. And a lot of times those new developers have different priorities or different ideas of what an ESB should do. They can provide a lot of expertise and new and fresh ideas that can make the open-source project a bit different than closed source, and provide some unique features.

One of the most fascinating things about the open-source community is something may not be my number-one requirement. But if it’s one of the other developer’s number-one requirements, they’re more than welcome to work on it and get it done. So in my mind it would have slipped. But in his mind it would have gotten done. It’s a fascinating environment.

For example, originally, when we were doing a lot of the Celtix stuff, we were still ObjectWeb, and Spring wasn’t really one of our priorities. From IONA’s standpoint, it’s not something that we’ve really experienced much with our customers. But as part of the merge with XFire, that user base was a little different than the Celtix user base.

Priorities got shifted, and we started developing more flexible models for deployment that allow the use of Spring, if you’re a Spring person. If you’re not a Spring developer, we have other options that are available to deploy your applications in a very different format that provides a lot of flexibility when you get that broad community throwing ideas out there.

There are definitely a lot of features being added that target a variety of users and use cases that really work into our original definition of what CXF was going to be. If you take a look at that Apache incubation project page, there’s a list of stuff. It was the original design of what this project was going to be. It’s going to have multiple bindings and multiple transports. We do have that, and that’s good. But with our growing list of cool features that developers keep coming up with, we’ve been adding all these multi-deployment capabilities. We’ve been adding a lot of these new WS specs like WS-Addressing and WS-Reliable Messaging.
Some of them weren’t even really anywhere close to final specs when we started the Apache CXF project. It’s a never-ending battle of more ideas coming at us, which is great — there are no complaints about that. But there’s definitely a lot of work to be done and a lot of new ideas. So, it’s a growing project with a growing list of features.

One of the other neat things about Apache is how many top-level projects they have. It’s in the 30s now, and a lot of the top-level projects have subprojects. So, there’s a lot of various functionality and different projects. One of the things that we’re trying to do from Apache’s success standpoint is reach out to some of those other communities, get involved with them, and help them get involved with CXF. Hopefully, we can work together to figure out the gaps that we have. Maybe we can use some of their technology, and they can use some of the CXF stuff.

The CXF runtime provides a lot of flexibility. We have a lot of interceptor points where core developers, who really know what they’re doing, can intercept various points of that message as it’s going through the system to do some partial processing or validation. We have some work in progress to do, like partial message encryption on some of the XML stuff. That’s done via some of these flexibility touch points, where developers can just take a part of the message and say, “Okay, we are going to encrypt this.” So, flexibility is another big word that’s important from a developer’s standpoint.

We’ve been working on some new features that we haven’t had in some of the previous generations of IONA’s SOA tool. Some of the main ones we have are the REST integrations. If you are not familiar with the Web 2.0/REST stuff, AJAX is the popular word that actually uses it. It’s a different style of interaction, where you do “gets” to get your XML data. Then it is a little bit processed on the client side, a little bit processed on the server side. There’s a lot of scripting going on in the marketplace today. There are a lot of JavaScript developers working with AJAX or doing other types of JavaScript, even on the server side. So, a lot of what we’ve done with CXF is to give those file developers some new tools to produce applications.

We’ve created a set of REST annotations. If you have existing Java services that you want to expose via REST capabilities, your AJAX clients can talk to them. You can annotate the code with these REST annotations, and CXF will pick up on them and do the REST or the SOAP interactions. We also provide support for writing your SOA applications in JavaScript. JavaScript is one of those neat interpreted things for rapid development, where you avoid some of that compile-repackage-redeploy cycle.

With the commercial product there are release cycles of six months or a year, or something like that. A lot of commercial vendors try to figure out what’s going into a particular release six months before it’s even released. So if those Web services specs aren’t finalized six months before release, they may not make that release cycle. In an open-source environment, where you have a constantly evolving development, as soon as these things get finalized, it can be made available almost immediately.

For developers that aren’t familiar with these things, it does give an opportunity to learn about them and use them in something that’s relatively easy. Expanding their knowledge is always a good thing from a career perspective. The more you know, the better off you are.

Read a full transcript of the podcast. Sponsor: IONA Technologies.

Listeners or readers of this podcast are invited to learn more about sponsored B2B podcasts.

 
icon for podpress  SOA and open source with IONA Technologies [40:36m]: Play Now | Play in Popup | Download (572)

ALM 2.0 era ushers application development into a managed business process

by Dana Gardner

Read a full transcript of the podcast. Sponsor: Borland Software.

Many people have defined software development as more art than science — sometimes even a dark art. That’s why the business side of an enterprise is often perplexed by the Application Lifecycle Management (ALM) process. They see what goes in as requirements, and see what comes out as functionality — but they often don’t understand what takes place in between.

Yet new trends are unfolding in ALM, called ALM 2.0, to help organizations transform software development and deployment into a managed business process. Dynamic applications and services oriented architecture (SOA) are also leading toward more componentized software, and that means more pieces to manage in design time as well as runtime. ALM 2.0 therefore points to the need to begin better coordinating between design phases and real-world use and efficiency of applications and services.

To help better understand the implications of ALM 2.0, and how Borland Software with its Open ALM approach is implementing it, I recently moderated a sponsored podcast with Carey Schwaber, a senior analyst at Forrester Research; Brian Kilcourse, CEO of the Retail Systems Alert Group and former SVP and CIO of Longs Drug Stores, and Marc Brown, vice president of product marketing at Borland.

Here are some excerpts:

If you look at most businesses today, IT organizations are expected to have very managed processes for their supply-chain systems and for their human resources systems, but when it comes to software delivery or software development, as you mentioned, there is this sense that software is some sort of an art.

We would really like to demystify this and put some rigor to the process that individuals and organizations leverage and use around software delivery. This will allow organizations to get the same predictability when they are doing software as when they are doing the other aspects of the IT organization. So our focus is really about helping organizations improve the way they do software, leveraging some core solution areas and processes — but also providing more holistic insight of what’s going on inside of the application lifecycle.

ALM isn’t just about developers. It’s really about all the roles that come together to ensure that software meets business requirements — from business analyst, to the architect, to the developer, to the project manager, the tester. And it feels like every year we end up with more specialized development teams than we had the year before. Specialization is great, because it means that we have more skilled people doing jobs, but it also means that we have more functional silos. ALM is really about making sure that every one of those silos is united, that people really are marching toward the same goal — to the same drumbeat. ALM is about helping them do that by coordinating all of their efforts.

In addition to functional silos, we’ve also got technology silos where we have a front-end in .NET, a back-end in Java, and maybe we’re using a BPM tool to create the entire composite application. There are just so many ways that this gets more and more complex. Then, in addition to managing roles, you also have to manage all of these different components and their interdependencies.

In the past, vendors have collected ALM solutions over time by acquiring support for each role. They’d acquire a tool that supported business analysts in the work that they do. Then, they’d acquire a tool that supported testers or test leads and the work that they do. They’d integrate the two, but that integration never ended up being very good. That integration is where ALM comes in. ALM lives in coordinating the work that the tester, the business analyst, and all the other roles involved really accomplish, to make sure that software meets business needs.

As most CIOs have done, I spent untold amounts of money trying to turn the software development process from an artistic activity to an engineering activity. There were a bunch of good reasons for that. One of them is that commercial computing is now over 60 years old. And one would think, at this point, that we would have figured out a way to commoditize it and make it more reliable. But it still remains, even after this long period of time, that software development is easily the most unreliable part of the whole value delivery equation that the IT department brings to the organization.

The fact that we are talking about ALM 2.0 is a big step in the right direction. In our business applications we need to be able to integrate at the information level and the data level, even if they are different code sets or physically different databases. From the business perspective we need to come up with one coherent answer to any kind of a business question. No matter what the toolsets are, we have one way to see them from a business perspective. I think that’s very encouraging.

We know from our business application stack that this is possible. So if it’s possible for the business, why isn’t it possible for the IT organization? You can call this a “cobbler’s children” problem. Why don’t we have for ourselves what we promise to deliver to our business associates?

SOA really does make quality that much more of an issue. We aren’t that good at it for basic, monolithic applications. Imagine how bad we’ll be at it with SOA? I really see SOA giving us an opportunity to do better, because in every service a defect is propagated to every single application that consumes that service. But if the service is high-quality, that quality level is propagated, too. Essentially we have a mandate to do a much better job on quality in our service