Ted Epstein

As enterprise teams move to adopt REST and modern API management, they are likely to encounter many of the same challenges that hindered, and sometimes derailed, SOA and earlier integration efforts. In particular, interoperability between systems is still a huge challenge for application developers, because each APIs uses its own vocabulary to describe the same essential business domain concepts.

A canonical data model is an ideal solution for this, often recommended, but rarely implemented effectively. Why is it so hard? And why doesn’t REST make these problems go away?

In this session, we’ll break down the challenges, and show how a shared canonical model can make life easier for API consumers, while still allowing the flexibility to expose different services, with different contextual requirements. We’ll explain why the right level of abstraction is so important for canonical models to address the pervasive problem of variability across APIs. We’ll formalize a realization mapping between canonical models and message definitions, and bring this together into a unified client SDK that works across services.