Skip to Content

Mapping one corner of the world – Two Patterns: Consumption vs. Integration

At the TechEd in Berlin, there were a variety of new technologies that were introduced (such as River) or already introduced innovations (such as Project “Gateway) where more details were provided.  What was missing was an indication of how these new technologies fit together and how they relate to the existing architecture.  There was often confusion, because the big picture was missing.

I’ve created a quick diagram of how these new developments relate to one another.  Obviously, I’m not going to include all technologies / innovations that were presented at the TechEds.

Initially, I’m not making a distinction between on-demand and on-premise offerings although the emergence of the on-demand has created the foundation for the new tools.

For me, the most important is the focus on the lightweight offerings that are REST-based and are primarily directed at the mobile market.  The basic desire is to increase usage of the fundamental business functionality in the Business Suite.   As Kaj van de Loo suggested at the Innovation Weekend “We need to open up our systems for consumption to all users. Project Gateway will help. Sybase UP will help too”. Equally important is the reassurance that the Enterprise Services aren’t going to disappear – indeed, without them, SAP would have had difficulty to move ahead with Project Gateway – but are focused on a different set of use cases. 

There are indications, however, that Gateway represents a shift for SAP. The development platform choices that are the platform targets for Gateway currently don’t include Java (see picture below) but focus on web-technologies not usually associated with enterprise settings (PHP, Rails, etc.).

Support through “Gateway” for mobile devices (photo: Frank Völkel) SOURCE

How does this new emphasis on lightweight applications relate to those “heavy” business processes for which SAP is so well-known? Slicing and dicing existing on-premise processes to fit this new model probably won’t be successful. The true challenge is to transform existing processes to reflect the inherent revolutionary qualities in these new devices.  Whether SAP has this knowledge or whether Sybase’s experience in mobile platforms will prove the necessary foundation for success is still open to debate.

A few points regarding this shift from Enterprise Service to a REST service created by Gateway

  1. The ability to create REST services based on Business Suite functionality is nothing new. DJ Adams has written about this possibility as early as 2004.  The novelty is that the creation of REST services is part of an official development tool.
  2. Previously, the creation of REST services was a development task. With Gateway, this task becomes more of a configuration task. The speed to create such REST services increases flexibility. The improved simplicity also provides the ability to create customized services that can directed to a specific user group. User mash-ups based on these simple REST interfaces are also easier than using the complicated SOAP interfaces in EnterpriseServices.
  3. Enterprise Services were defined by SAP in cooperation with the ecosystem. I haven’t heard anything about a set of REST services that will be created by SAP – standard REST services that are available out-of-the-box.  Thus, there may be a governance issue that must also be considered.
  4. I haven’t heard much about how authentication works when using these new REST services.
  5. The fact that SAP is using open standards such as oData, JSON and ATOM in Project Gateway is a good sign and shows that SAP is aware of the importance of developments outside of the enterprise software space – at least where the use of such developments makes business sense.
You must be Logged on to comment or reply to a post.
  • By supporting REST-based services, they are definitely targeting a whole new set of developer communities. But nonetheless, Gateway is still only a technology enabler. I suspect the challenge of composing the actual business objects to be exposed via Gateway will remain.
    • Do you have access to TechEd session materials? There was an interesting session in Berlin called "Accelerating Consumption for Networked and Mobile Solutions Through Project "Gateway."" that provided some more details about consumption patterns - there is even the ability to perform screen-scraping - easy enough. What I didn't see however was how you create complicated REST services that bridge particular transactions or business objects. You may be right - the creation of such services might be more difficult.


  • Nice blog post, thanks Richard. The diagram is especially clear and useful.

    I re-read my article from all those years ago; SAP's disclaimer sentence still makes me smile: "DJ Adams is not an SAP employee and the opinions he expresses in this article do not reflect the official opinion or positioning of SAP.". I wonder if that's changed now? 😉

    Anyway, I just wanted to make the point that consumption does not necessarily just mean read-only. Especially in the context of consumption using the HTTP application protocol.

    Cheerio for now

      • Hi Dick

        Loose vs Tight?

        Flexible vs Brittle?


        Seriously though, perhaps if framed as an approach or orientation, if you're looking for one word, then I'd suggest:

        [Orientation:] Resource vs Service


        • dj,

          I've seen you mention the shift from service to resource orientation in some of your tweets. I'd like hear more about the technical and "philosophical" impact of this change.

          Do you take blog request? :->


  • Hello Richard,

    Thanks for this blog.

    Can you explain to me how you would define both patterns (outside of used protocols/technology)? I.e. from a more conceptual level?

    Thanks in advance!

    Kind regards,

    Maarten Engels