Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations REST-based Integration Architecture for a Financial Business Service

REST-based Integration Architecture for a Financial Business Service



Phillip Ghadir presents a financial application that was initially built using SOAP, WSDL, WS-*, and was later migrated to use REST, Atom, and AtomPub, explaining the decisions made, the pitfalls and the lessons learned along the way.


Phillip Ghadir, CTO and principal consultant of innoQ Deutschland GmbH, has built several systems and components for large scale, distributed, mission critical systems that are still serving continuously until now. He was involved in several projects, including a large development effort for building a Basel II- compliant rating service, where he was the lead architect.

About the conference

QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.

Recorded at:

Oct 13, 2009

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • How to make the service to rate a customer?

    by Tiberiu Fustos,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I watched carefully the presentation here, but I think the most interesting part came at the end, but unfortunately I still don't get it: the presentation focused on navigating an object graph and creating objects/entities. What I didn't get is how was the core capability of the service being invoked - the "rate operation" talked about at the end. Does one "create" an empty rating, somehow links it with the customer and then does again a GET to see what the rating is? How do I tell the system "please rate it for me now" (or is this a "side-effect" of create/read/update of a resource)?
    Another thing I was wondering about is how the initially mentioned problems were actually solved with the new solution - what happened to the MDA approach, how easy/difficult was it for the B2B consumers to use the new service, versioning etc.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p