Microservices Expo Authors: Liz McMillan, Pat Romanski, Carmen Gonzalez, Elizabeth White, Jason Bloomberg

Related Topics: Microservices Expo

Microservices Expo: Article

Dion Hinchcliffe's SOA Blog: Creating Open Services That Last And Anyone Can Use

I just finished up a podcast discussion this evening on Web 2.0 and Global SOA with David Linthicum

I just finished up a podcast discussion this evening on Web 2.0 and Global SOA with David Linthicum that he was kind enough to host on his popular SOA Expert Podcast show.  We were discussing how the software worlds are rapidly converging into each other with mash-ups and Ajax helping drive a seemingly unquenchable demand for open services on the Web.  All of this while individual organizations themselves are trying to build almost identical service ecosystems behind the firewall and create their own type of mash-ups, known as composite applications.  They are also increasingly integrating them into their very own internal business processes. 

And developers everywhere have started accessing the hundreds (and soon thousands) of terrific open Web 2.0 software services available on the Web in order to plug them into their own software. Either just for their own purposes or to put them in their organization's own software.  Mash-ups and service reuse are an intriguingly grassroots phenemonon that will only increase dramatically in 2006.  Thus it will be a largely Web 2.0-driven story.  This convergence of use, which we talk about in the podcast and my recent cover story on the subject, is triggering what David calls a push from outside-in that will eventually cause most everything to integrate together.

An important reason why the Web is now the  world's biggest and most important computing platform is that people providing software over the Internet are starting to understand the law of unintended uses.  Great web sites no longer limit themselves to just the user interface they provide.  They also open up their functionality and data to anyone who wants to use their services as their own.  This allows people to reuse, and re-reuse a thousand times over, another service's functionality in their own software for whatever reasons they want, in ways that couldn't be predicted.  The future of software is going to be combining the services in the global service landscape into new, innovative uses.  Writing software from scratch will continue going away.  It's just too easy to wire things together now.  Witness the growth of truly amazing mash-ups of which things like Retrievr and Meebo are only two tiny examples.

Service Models: So Many Choices

Figure 1: The wilderness of service models.  What to choose?

The world of traditional software integration has long had its favorite tools like SOAP and JMS.  But these service types tend to be far too controlling of the other side of the conversation. And they generally require special (and often expensive) tools to use.  And the Internet just loves to route around complexity.  Folks want the easiest thing that works to get their Ajax client connected or to wire their mash-up together with your services.  So favor simple and elegant over complex and hard-to-use.  Start looking hard at RSS, REST, maybe even SSE

And if you want your services to stand the test of time, and you want anyone to use them, you need nice, clean XML formats, or maybe even JSON.  Forget XML schemas.  You can always use the hard stuff if absolutely nothing else will do the job, but generally you won't need them. 

Low barriers
to reuse, frictionless integration, widespread reuse.  These are the mantras of Web 2.0. 

OK, so how do you do it.  How do you deliver an API for your services that lasts and anyone can use.  There are a few things to worry about
  • Scalability: Simpler is more scalable.  This is particularly true of REST.
  • Ease of Consumption: XML/HTTP is easier than SOAP. JSON is the easiest for Ajax.  And Bittorrent, possibly the hardest however definitely the most intrinsically scalable.
  • Tool Support:  Reinventing the wheel is for losers.  Use good libraries and tools.  This favors SOAP, but increasingly REST is getting solid tool support.  Certainly XML has really good tools. And JSON doesn't really need many.
  • Security: Yep, this is going to be huge for Web 2.0, but it's already critical inside most organizations today.  SOAP certainly has the goods here but really good encryption toolkits are doing just fine on the rough and tumble Web too (witness Meebo's ballyhooed 1024-bit password encryption.)

In the end, XML over HTTP, and REST, and particularly RSS, will be the lowest common denominator on the Web.  Organizations experiencing the outside-in forces David Linthicum talks about are going to have to figure out how to bring in these simpler services and trust them.  It's going to be an increasingly important topic as the boundary of IT systems, the Web, and mobile devices starts to blur seriously over the next few years.

And folks are starting to provide real support for true Web 2.0 service styles with examples like the Restlet library for Java, which  eWeek says is specifically designed for delivering Web 2.0 services.

Of course, like I discussed in previous articles, scalability is going to be the most difficult issue for successful Web 2.0 software.  You'll need to plan for radical decentralization early on if you're going to survive your own growth curve.  But Bittorrent solutions for Web services are finally avaiiable including Prodigem's mind-blowing Auto RSS Torrent which takes your RSS feeds and turns them into BitTorrents.  This isn't an example of REST or SOAP with BitTorrent behind it to make it infinitely scalable, but it's a start.  Expect lots more as the services worlds not only collide but turn upside down as well.

How will Web 2.0 open APIs ever scale without a new generation of Web services to support it?

More Stories By RIA News Desk

Ever since Google popularized a smarter, more responsive and interactive Web experience by using AJAX (Asynchronous JavaScript + XML) for its Google Maps & Gmail applications, SYS-CON's RIA News Desk has been covering every aspect of Rich Internet Applications and those creating and deploying them. If you have breaking RIA news, please send it to [email protected] to share your product and company news coverage with AJAXWorld readers.

Comments (1)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Microservices Articles
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, will discuss why containers should be paired with new architectural practices such as microservices ra...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...