Currently browsing webservices


Welcome, New Year, and Other Miscellaneous Things

Sun, 25 Jan 2009 2:42 UTC

We’re well into the New Year—24 days to be exact—and I’ve long since been putting off this post, but it’s not really a single post. Instead, it’s a collection of things that I’ve been wanting to say but have been putting off, and it’s a look forward to things I’m working on, would like to see happen, or would like to be involved with this year. So, rather than the obligatory look back at what I did last year, this is a look forward at what I’m interested in for the coming year (in no particular order).

First of all, I would like to offer some congratulations to a handful of friends of mine. These congrats have been a long time coming from me and are already old news to many of you. In no particular order, I want to congratulate: Andrei Zmievski on being hired as an Open Source Fellow at Digg; Jon Tan on taking a role as the new Creative Director at OmniTI; Cal Evans, who moved to the Netherlands to be the Director of the PHP Centre of Expertise at Ibuildings; Marco Tabini and Keith Casey for launching Blue Parabola, and Matthew Turland for joining them; Eli White for accepting a position at Zend as the Zend Community Manager/Leader & DevZone Editor-In-Chief; and last, but not least, Brian DeShong for his promotion to Director of Technology at Schematic.

Next, I wanted to take a moment to mention and promote the writing I’ve been working on. I didn’t publish a single thing last year, and in 2007, I published only one article, so I resolved this year to get off my ass and remedy this. In February, php|architect will publish my article entitled “Grokking the REST Architectural Style.” This article attempts to explain what Representational State Transfer really is by going beyond peoples’ fascination with designing URLs, using XML, and focusing on HTTP methods. Instead, I’ll look at the real heart of REST with hopes that readers will fully understand what it means to build a RESTful application. A fellow web services aficionado said of the article, “I think you expressed very nicely what the concepts are all about—and without a URL or HTTP verb in sight!”

Following the REST article, in March php|architect will begin publishing my monthly column “From the Cloud.” In “From the Cloud,” I’ll be looking at practical web services you can use, as well as exploring trends that are transforming the way we use the Web. Here’s a quick blurb from the column that describes its focus:

As the Web matures and enters its third decade of life, many services are turning to cloud-based models of data storage. End users are becoming more and more comfortable with the notion that their data lives in the ether of the Internet rather than on their personal computers. Finding that data, retrieving it, manipulating it, and using it in meaningful ways are the challenges that face the era of the intelligent Web. I hope you’ll join me each month as we explore these services and technologies From the Cloud.

Finally, later this year, php|architect will publish another article I’m working on that will take a practical look at using HTTP in your applications in a RESTful way. There may also be a book idea or two in the works for me, but more on that later.

Oh, and I also had the privilege of being invited again to write a PHP Advent post during the month of December. I wrote a post entitled “Practice Safe & Idempotent Methods.”

Furthering my ramblings in this post, I also wanted to mention some community projects I’m working on this year. As always, I’d like to see PHPCommunity.org evolve and grow into a real website that offers real value to the PHP community, so that’s on my list of things to do. I’ll post more on that in the future. In addition, I have some plans for Atlanta PHP this year that include a new website, incorporation so we can accept donations, and an event to occur later in the year, but you’ll hear more from me about this as the details are finalized. Inspired by my own writings for the “From the Cloud” column, I’ll also be developing a PHP library of classes for interacting with various web services. This began with the Amazon Web Services library in PHP project, but I’ll be migrating that elsewhere to be part of a larger project in the near future, so be on the lookout for that.

Last, but not least, I wanted to mention the website that I built for my dad over the holidays. He recently launched his own business, Small Business Resource Associates, that provides services to small businesses and commercial real estate investors. I did all of the HTML/CSS and PHP programming for the website, while my aunt did the design work. It was an interesting project for me because I haven’t really touched front-end (client-side) web development in several years (I stick mainly to back-end, server-side development these days), and I was proud that I was able to make a website that validates successfully as XHTML 1.1. Another interesting part of the site is that it has a blog, something that I don’t believe many in the financial services industry are doing, so I think that’s one thing that sets apart Small Business Resource Associates from the competition. If your small business is looking for a loan, business plan, business consulting, SBA help, etc., please check it out.

Well, that’s a wrap. I’ve got a growing list of topics I want to blog about, so I hope that you’ll be hearing much more from me this year than you did last year.

Happy New Year!

Comments 1 Comment »  Permalink Permalink  Tags Tags: , , , , , ,


The Death of SOA?

Wed, 7 Jan 2009 16:35 UTC

Someone at the office sent around a link to an InfoWorld article that discusses a blog post made by Anne Thomas Manes, vice president and research director at Burton Group, in which she announces the death of SOA.

I thought my response was worthy to share on my blog, so here it is:

It’s an interesting argument she makes in the obit. She’s saying that the term “SOA” has become confusing and, thus, misleading. All it is anymore is marketing-speak, just like “Web 2.0.” Everyone and their brother has a different idea of what Web 2.0 means, and I suspect the same has happened for SOA. However, she says that “although the word ‘SOA’ is dead, the requirement for service-oriented architecture is stronger than ever.”

She goes on to say that “successful SOA (i.e., application re-architecture) requires disruption to the status quo. SOA is not simply a matter of deploying new technology and building service interfaces to existing applications; it requires redesign of the application portfolio. And it requires a massive shift in the way IT operates.”

What is required is good software architecture, not simply throwing on layers and layers of other services and hoping for the best.

I think this is her own attempt to disrupt the status quo. She wants to do away with the terminology because it has clouded the real issue. What’s the real issue? She highlights this when she concludes: “and that’s where we need to concentrate from this point forward: Services.”

IMO, bolting on services should never become a replacement for good software architecture, and I think that’s what has happened in many cases with SOA. Instead, we need to really think about and design how services fit into an “application portfolio.”

Comments No Comments  Permalink Permalink  Tags Tags: , ,


Slides from php|works & PyWorks

Wed, 3 Dec 2008 4:00 UTC

Here are the slides for my talk “You Look Like You Could Use Some REST!” given on the general track at php|works and PyWorks in Atlanta a few weeks ago. In my talk, I mentioned that I would be adding my notes from the talk to this blog post, but I’ve decided against doing that for the time being. However, I’ve been thinking about REST a lot lately, and I’ll use this blog in the near future to write some of these thoughts. I’m also working on a now overdue article on REST for php|architect, and I’m sure my editor would not like it if she knew I was blogging about REST instead of writing my article about it. I’ll announce that article here when it’s published so you can go snag a copy.

I will say this one thing, though: In my talk, I mentioned that the REST community doesn’t care much for content negotiation. I simplified the issue, though, because there are really two camps. On the one side, you have those who think content negotiation is the only way to go, and on the other side, you have those who prefer file extensions or query string parameters that denote the content type to return. There is actually an interesting discussion about a proposal to use a type attribute in the a tag in HTML 5 to tell the client what content-type to request for the resource identified by the URL in the href. It might look something like this:

<a type="text/html" href="/user/ramsey">Ben Ramsey</a>, 
<a type="application/pdf" href="/user/ramsey">Ben Ramsey (PDF)</a>

And with that, I leave you with the slides for my talk…

Representational State Transfer, or REST, has become the hip, new buzzword of Web 2.0. But what really makes an application RESTful? Is it pretty URLs? Or the use of XML over HTTP? Is it any web service that doesn’t use SOAP? In all of the hype, the definition of REST has become clouded and diluted.

It’s time to take a fresh look at REST. In this talk, Ben Ramsey reintroduces REST and its architectural style. He shows that REST is not only an architecture for web services but that it describes an architecture for the Web. Ramsey will demonstrate how statelessness, a resource-oriented architecture, atomicity of requests, and other traits of REST make the most of the Web’s architecture to provide scalable and simpler web services turning the Web into a platform by which rich clients can access and manipulate data.

Comments 1 Comment »  Permalink Permalink  Tags Tags: , , , ,


XML & Web Services Slides

Tue, 31 Oct 2006 23:12 UTC

I’ve just finished giving my presentation on XML & Web Services with PHP (An Overview). Overall, I think the presentation went quite well, though I had entirely too much material to cover in a very short period of time, so it was impossible to go into much depth on any one type of Web Service. This was unfortunate, but I think the “overview” nature of the presentation allowed for this top-level approach.

As promised, here are the slides from the presentation (PDF, 2 MB), and what follows is the list of links for further reading:

Further Reading

XML-RPC

Comments 1 Comment »  Permalink Permalink  Tags Tags: , , , , , ,