Private Sector API Codesign PART II – Bogdan Dumitriu
summary
Pilot of a REST API profile for CEF eDelivery defines a core (transport security, TLS baseline, auth), an extensible set of domain endpoints and fixed messaging endpoints to wrap/unwarp messages across networks, and tests HTTP/2, JSON/XML payloads and server auth via identity providers; it targets browser and mobile clients as well as server‑to‑server, offers optional reliability/non-repudiation, and asks whether to bridge via AMQP/MQTT, what metadata enables interoperability, and which versioning model (endpoint, payload, metadata) works best.
AI-written summary · about
chapters (8)
- 0:00Start
- 16:50Is there a recommended/predefined set of metadata that could be included in a generic REST API profile in order to facilitate interoperability with third-party message or data exchange systems?
- 18:36In an asymmetric REST API profile, with the client and server roles fixed, what is the best approach to support asynchronous communication in a business sense (polling vs web sockets vs other approaches, mistakes to avoid)?
- 21:03What other options would you recommend in order to establish server identity and server trust in addition to TLS?
- 24:09What is a recommended approach for defining a generic (business agnostic) REST API profile?
- 24:25QB: What should be designed as part of a generic REST API profile to support service discovery? Are there recommended (tested) models that work better than others?
- 25:17What are the relative merits of different approaches to versioning (in endpoints, in payload, multiple)?
- 25:46AMQP and MQTT are often quoted as alternatives to REST. Could you share any experience you have with these protocols?
related talks
19mREST, SOAP, Hypermedia: When, why & how to use what
26mFrom project to reality let's explore some API
21mAPI Design in FinTech: Challenges and Opportunities for next-gen APIs.
24mMastering API Security: From Design to Deployment
42mThe future of API (Platform) architecture
27mBuilding Great Web APIs
47mBuilding APIs your users will want to use
27mThe API Design Strategy You Need for Growth