Craig Hughes

VP Architecture at Emirates NBD

Message Posts: 17 Comments: 3

Bio Previously, Chief Enterprise Architect, with a focus on APIs for Danske Bank. Please note that views expressed here are my own and do not necessarily express those of Danske Bank or Emirates NBD. Career History A specialist in API and web technologies, with a strong focus on APIs. In Danske Bank I was responsible for breaking the core banking systems into business domains and, using these as the building blocks, create reusable business process via APIs.

Blogs

API

Chain of Trust

24 Feb 2019

In the traditional two or three-tier world of web development, there is an inherent trust between the client and the server. Each is contextually aware of the other and withholds or shares information depending on the level of trust. The server may generate and persist session information about the client to enforce control or to simplify interac

API

API Misconceptions

01 Feb 2019

I’d like to clarify some things about the use of HTTP verbs for RESTful APIs and the apparent misconceptions these can bring about. Firstly, there are a few people who believe that RESTful APIs are predominantly for CRUD (Create, Read, Update, Delete) operations. I covered how this can be extended to other operations in a previous article; Nouns

API

API Fragments - simple flexibility

27 Jan 2019

Designing APIs often leads to a compromise between producers and/or consumers. Consumers of APIs would like the interface to be as close to their requirements as possible; they want to avoid possible composition or contract navigation. API producers would like their interface to be as simple as possible; they want to support maximum reuse and con

API

API: Arrays or named elements?

15 Jan 2019

The humble restaurant menu follows a common pattern where menu items are generally separated into a logical hierarchy. At the top level, we may have breakfast items, dinner items or drinks items. Each of these could be grouped further into categories like meat dishes, fish dishes or pasta dishes (dinner items), and again into burgers and steaks (m...

See all Craig's blogs

Craig is Commenting on

Should APIs be Pre-made or Deli style?

Thanks for the questions Ketharaman. Your first question regarding the sensitivity of data being shared. We currently use the scopes within a JWT to define if sensitive portions of the data elements can be presented in the response. Quite simply, if an authenticated user does not have the scope (authorization) required for a portion of the data within the API response, then these elements are omitted. For obvious reasons, supporting documentation needs to expand on this. Secondly, you mentioned that using the third option could result in a very large dataset - which could be compared to a file dump. It is possible that this could be the consequence if you allow your consumer to “select all”. However, there are approaches you can deploy to avoid this, including: Paging (limiting the response to a maximum number of records) Hyperlinking (or HATEOAS) - providing links to internal entities instead of the data (supporting discovery) Or option 2 - the Deli-style approach when requesting lists of data - let the consumer decide which elements make sense in a list in order to find the single entity being sought. Thanks, Craig

15 Oct 2018 Reply Read article

The Butterfly Effect

@João Thank you! I have sent you an email. Craig

11 Sep 2018 Reply Read article

The Butterfly Effect

@João, Thank you for your comments and insight. I'd be keen to see your BotF diagram once you have it completed.

09 Sep 2018 Reply Read article