INNOVATE. INSPIRE. DELIVER. - IFSF · Title: PowerPoint Presentation Author: Richard Haddon Created...

INNOVATE. INSPIRE. DELIVER.

Recommendations on IFSF’s API Strategy and Architecture

AGENDA

Michael de SelincourtIntegration Architect

Bryan BlackCTO

Chris GriffithsManaging Partner

Tim LinsellConsulting Partner

Charlotte GyetvaiEvent Manager

REPL GROUP

► Offices in four regions: Americas, UK, Asia & Africa

► Now employing over 300 Remarkable People

► 40% average growth per annum over 10 years

► Experts in fuels retail and Integration

STRATEGY REPORT

► IFSF is working on a third generation of standards, using HTTP instead of LonWorks and TCP/UDP/IP

► As invited by IFSF, this summer REPL reviewed IFSF’s work-to-date and intended future direction.

► We:

► Reviewed IFSF’s documentation and tool and language choices► Interviewed the board, and certain suppliers and partner bodies (including Conexxus)► Synthesised the findings into recommendations and delivered a report to the Board

► This presentation is largely based upon the findings in the report.

► For more detail, please refer to the full document (or talk to us at the conference!)

INDUSTRY CHANGE

Ranking by market capitalisation, Bloomberg and PwC 2019

Rank Company name Location Sector

1 Microsoft United States Technology

2 Apple United States Technology

3 Amazon.com United States Consumer Services

4 Alphabet United States Technology

5 Berkshire Hathaway United States Financials

6 Facebook United States Technology

7 Alibaba Greater China Consumer Services

8 Tencent Greater China Technology

9 Johnson & Johnson United States Healthcare

10 Exxon Mobil United States Oil & Gas

INDUSTRY CHANGE

Vendors and retailers will continue to benefit from easily integrated forecourt technology, even as the industry’s participants transition to more modern integration technologies.

IFSF’S VISION FOR APIs

► IFSF should refine its ways of working to remain relevant in its interoperability mission.

► IFSF would be at risk of irrelevancy without modernisation initiatives like those reviewed, but IFSF is subject to significant constraints and in an environment of accelerating change.

SUMMARY OF RECOMMENDATIONS

► IFSF should refine its ways of working to remain relevant in its interoperability mission.

► IFSF would be at risk of irrelevancy without modernisation initiatives like those reviewed, but IFSF is subject to significant constraints and in an environment of accelerating change.

SUMMARY OF RECOMMENDATIONS

VALIDATE DIRECTION

AIM TO MATCH THE WORLD’S BEST PROJECTS IN USABILITY

LOOK BEYOND REST

VALIDATE DIRECTION

REVIEW OF THE WORK SO FAR

Document Rating

2-03 Communications over HTTP/REST

4-01* Design Rules for APIs (OAS 3.0)

Part 4-01 Design rules for JSON

4-05 (1) ReMC API

4-05 (2) Implementation Guideline mostly out of scope

4-10 WSM API see notes

4-15 Pricing API see notes

API Transport v0.3

4-02 (1) Core Libraries JSON Schema deprecated in favour of OAS

4-02 (2) Core Libraries RAML deprecated in favour of OAS

Tool Rating

Custom Portal

Docker

Eclipse with KaiZen see notes

GitLab

Imposter

Jenkins

OAS 3.0

swagger-cli

swagger-ui

No significant concerns Some changes or actions recommended

Significant action needed Out of date or scope, or beyond our ability to assess

OUTCOMES AND EFFICIENCY

Prioritisation from Strict to Discretionary

It is very useful for IFSF to be quick and strict on correct representations (e.g. a JSON carwashPrice)

It is useful for IFSF to issue clear guidance on synchronous vs. asynchronous options

It is not very urgent for IFSF to be strict on URL structures (because these are easy to transform)

It is not urgent for IFSF to forbid specific HTTP status codes or headers

OUTCOMES AND EFFICIENCY

Prioritisation from Strict to Discretionary

Separate data from transport!

IFSF & its partners are the world experts in forecourt data

They are less well positioned to issue guidance on e.g. the merits of HTTP/3

IFSF’S STRATEGIC BALANCE

CAUSE INCONSISTENCYFLEXIBILITY

RUSH INTOWRONG DECISIONS

DISINCENTIVE TOSUPPORT IFSF

OPENNESS

STIFLE INNOVATION,DISINCENTIVISE USE CAUSE INCONSISTENCYFLEXIBILITY

TOO LATE,LEFT BEHIND

BARRIERS TO ADOPTION

OPENNESS

STIFLE INNOVATION,DISINCENTIVISE USE CAUSE INCONSISTENCYFLEXIBILITY

TOO LATE,LEFT BEHIND

BARRIERS TO ADOPTION

OPENNESS

IFSF ‘picks its battles’

Setting useful standardsIn time to be adopted

As open as possible

MATCH THE WORLD’S BEST PROJECTS IN USABILITY

OUTCOMES AND MODERN TECHNOLOGY

Open Standards and Paid Services

Twitter API public documentation

Twitter wants people to use its API; so it makes clear documentation

available to anyone for free

OUTCOMES AND MODERN TECHNOLOGY

Open Standards and Paid Services

Google Maps API pricing model

It is commonplace to charge for APIs This Google Photo API costs 0.7¢ per use

MODERN COLLABORATIVE METHODS

An API portal hosted on GitLab.io

It would be easy to host IFSF’s interactive API

documentation on a free hosting service

React.js’s pull requests

Error found and a correction

volunteered by a community member

Automatically validated by the

system

Reviewed and approved by an administrator

Opportunity for community to discuss

the change

6000 users are subscribed to updates

on the project

MODERN COLLABORATIVE METHODS

React.js’s community collaborating online

“Can anyone help me with this technical

question?”

“Here’s where to look for help on that question”

“Here’s why the code behaves that way”

LOOK BEYOND REST /

ARCHITECTURAL

DIRECTION

LOOK BEYOND REST

Can’t REST do everything?

RESTful Web Services are good!

They are simple.

They are almost universally understood and supported.

REST FACILITATES A MODERN ARCHITECTURE

Cloud providers

App Service

Simulators

SimulatorsDevices

under testPOSTMAN &

newmanImpostor

LOOK BEYOND REST

Servers

POSes(CDs)

Peer to peer discovery (UDP)

POSes(CDs)

Peer to peer discovery (UDP)

LOOK BEYOND REST

But…

REST Web Services originated in client-server connections to relatively static services advertised through Domain Name Services

IFSF’s existing design is a dynamic, decentralised/peer-to-peer environment.

Consider some other decentralised systems:

• Internet of Things (e.g. Smart Home systems)• BitTorrent (peer to peer file sharing)• Distributed Ledgers (notably Cryptocurrency)

These domains use, but do not limit themselves to RESTful web services.

Servers

POSes(CDs)

Peer to peer discovery (UDP?)

Peer to peer communication (HTTP/TCP)

POSes(CDs)

Peer to peer discovery (UDP?)

Peer to peer communication (HTTP/TCP)

Site AP

A POSSIBLE REST ARCHITECTURE

IMPLIED TCP ARCHITECTURE

LOOK BEYOND REST

► IFSF is a bidirectional protocol, both synchronous and asynchronous► You can broadcast a heartbeat over LonWorks► You can broadcast a heartbeat over UDP/IP

► REST is a client-server synchronous architecture and has no ‘broadcast model’

► Must every device on the forecourt be an HTTP server?► Must every device maintain TCP connections to every other interesting device?

► Could you support broadcast & asynchronicity without a ‘mesh’ of TCP connections?

WHAT WOULD IoT DO?

Servers

POSes(CDs)

FPsPOSes(CDs)

Gateway & Broker

Peer-to-peer messaging Peer-to-peer messaging

WHAT WOULD IoT DO?

IoTMessageBroker

BackupIoTMessageBroker

IN SUMMARY

Look Beyond REST

Isolate Data & Transport

Work in prioritised increments

Open standards

SaaS Simulators

Commodity Portal

Online Collaboration

Website: https://www.replgroup.com/LinkedIn: https://www.linkedin.com/company/repl-group/Email: chris.griffiths@replgroup.com

CONTACT US

INNOVATE. INSPIRE. DELIVER. - IFSF · Title: PowerPoint Presentation Author: Richard Haddon Created...

Documents

BEE ZPVS EFTJHO IFSF

IFSF POS to EPS · 2018. 6. 13. · Jan 2012 Updates - V2.5 June 2008 Connexus Interface Specification V1.0 Describe the Connexus use of IFSF POS-EPS July 2005 IFSF POS to EPS implementation

IFSF POS to EPS

Livre arbítrio charles haddon spurgeon

Acidentes, não castigos (charles haddon spurgeon)

Tokheimmid.tokheim.com/pdf/TOKHEIM-EVAL-C012-WWC-TC7138-REV56V.pdf · 2016. 1. 6. · WWC-EIN 3.21 (checksum: OxD7FD) WWC-IFSF 3.34 (checksum Ox8CA9) WWC-IFSF 3.35 (checksum Ox6FD6)

Graças fragantes charles haddon spurgeon

Amor charles haddon spurgeon

16 ISS Baker Haddon 1974

2014 Technical Conference IFSF Mobile Payments Standard...FEP Online Host 2 POS IPT OPT IFSF P2F & Security HSM HSM PVVs & cards IFSF H2H & Security Online Host 1 HSM Online Host 3

Hillset, 10 Haddon Drive, Bakewell, DE45 1BDHillset, 10 Haddon Drive, Bakewell, DE45 1BD · 2020-05-15 · Hillset, 10 Haddon Drive, Bakewell, DE45 1BDHillset, 10 Haddon Drive, Bakewell,

Barrabás (charles haddon spurgeon)

REMOTE INSPECTION OF THE IFSF SPENT FUEL STORAGE RACK

4UBSU IFSF GPS DBMMCBDLT

IFSF-LON® from Proprietary Protocol Converterbetacontrolusa.com/images/phocagallery/cerpacky/ke_stazeni/PKONV... · IFSF-LON® from Proprietary Protocol Converter fuel sites Features:

Haddon & James

Haddon Twp. Flood Repairs

DDFQUFE IFSF

Tokheim MID | Download Centremid.tokheim.com/pdf/TOKHEIM-EVAL-C012-WWC-TC7138-REV54V.pdf · 2015. 7. 7. · WWC-EIN 3.21 (checksum: OxD7FD) WWC-IFSF 3.34 (checksum Ox8CA9) \MNC-IFSF

INSPECTORES FISCALES SIN FRONTERAS · Buenas noticias para IFSF en 2018 Por James Karanja, Director de la Secretaría de IFSF En octubre, la OCDE y el PNUD presentaron el Informe