BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Web Services Content on InfoQ

  • Addressing Doubts about REST

    Invariably, learning about REST means that you’ll end up wondering just how applicable the concept really isbeyond introductory, “Hello, World”-level stuff. In this article, Stefan Tilkov addresses 10 of the most common doubts people have about REST when they start exploring it, especially if they have a strong background in the architectural approach behind SOAP/WSDL-based Web services.

  • Getting Started With SharePoint Web Services

    Programmatic access to SharePoint is limited to .NET based languages unless a developer utilizes web services. Trent provides examples of how to extend the out of the box web services and how to consume them from both .NET and Java.

  • Process Component Models: The Next Generation In Workflow ?

    Tom Baeyens, founder of JBoss jBPM gives his view of the state of the BPM / workflow market and introdces a new type of workflow technology called process component models.

  • Hypermedia in RESTful applications

    One of the constraints defined for the architectural style known as REST is "hypermedia as the engine of application state". Mark Baker, well-known for being one of the first who advocated the REST style instead of the mainstream web services approach, discusses that the hypermedia constraints means in practice and why it is essential to RESTful design.

  • "Can I call you back about that?" Building Asynchronous Services using Service Component Architecture

    This article discusses the need for asynchronous services when you build an application using a service-oriented architecture. Building asynchronous services can get complicated, but is made straightforward using Service Component Architecture (SCA). The steps involved in using SCA to create an asynchronous service and asynchronous service client are described in this article.

  • Introduction to NetKernel

    NetKernel is a software system that combines properties of REST and Unix into an abstraction called resource oriented computing (ROC). The core of resource oriented computing is the separation of logical requests for information (resources) from the physical mechanism (code) which delivers it. This article provides an introduction to the NetKernel framework.

  • Interview and Book Excerpt: Nicolai Josuttis, "SOA in Practice"

    Today, InfoQ publishes a sample chapter from Nicolai Josuttis' "SOA in Practice". On this occasion, InfoQ's Stefan Tilkov had a chance to sit down with Nicolai to ask about his views on SOA, the main industry misconceptions about it, key success factors and a recommendation for how to approach it.

  • Talking Rails 2.0 with David Heinemeier Hansson

    Ruby on Rails 2.0 is the next version of the premier web application framework for the Ruby language, after almost a full year in development. Rails 2.0 is full of great new features, bug fixes and lots of the polish expected from the team. InfoQ had the opportunity to talk with the creator of Rails, David Heinemeier Hansson, to learn what it's like to get this release out the door.

  • A Brief Introduction to REST

    In this article, Stefan Tilkov provides a pragmatic introduction to REST (REpresentational State Transfer), the architecture behind the World Wide Web, and covers the key principles: Identifiable resources, links and hypermedia, standard methods, multiple representations and stateless communication.

  • The Seven Fallacies of Business Process Execution

    After 8+ years of intense research, the promises of BPM have not materialized: we are still far from having the ability to use the business process models designed by business analysts to create complete executable solutions. Some argue that we need to re-engineer BPM standards. In this paper we explore a new architecture blueprint for BPMSs that offers a cleaner alignment between SOA and BPM.

  • Asynchronous, High-Performance Login for Web Farms

    Often during my consulting engagements I run into people who say, "some things just can't be made asynchronous" even after they agree about the inherent scalability that asynchronous communications pattern bring. One often-cited example is user authentication - taking a username and password combo and authenticating it against some back-end store.

  • Setting out for Service Component Architecture

    Henning Blohm, Java EE Software Architect at SAP and Co-Chair of the SCA-J Technical Committee provides his perspective on Service Component Architecture as a cross-technology programming model integration. He argues that for vendors, SCA lowers the marginal costs of providing implementation or binding technology to its users and for users SCA reduces the marginal costs of making use of them.

BT