From models to hosted OpenAPI Specification (OAS)
Karel has participated in all aspects of the solutions lifecycle from problem structuring, feasibility, solutions architecture selection, technology scanning, negotiating with vendors, implementation, deployment and user support.
These solutions entailed products for desktop, terminals, client/server, dynamic web content and multi-tier web applications addressing persistence using XBase libraries, RDMS’s (Oracle, MS, Sybase, Interbase), ORM’s (Object-Relational Mappers), NoSQL, XML-technologies and object stores.
Developed products ranged from simple CRUD systems with extensive reporting to decision support systems with high-value-addition processing.
Solutions were developed with degrees of tool-support ranging from little or none up to fully generated solutions.
Karel closely tracks processes and methods and their match to organizational capacity.
Translate a data model of a domain into a hosted, fully functional OpenAPI Specification (OAS)
with minimal coding by integrating PostgreSQL with PostgREST and NGINX.
This presentation goes beyond a trivial CRUD (Create/Read/Update/Delete) API reflected from the schema,
to a State Model of a domain entity and its life cycle. It is rather the PostgreSQL functions
achieving the state transitions in the entity life cycle, that are exposed as idempotent API endpoints.
Hence the API is realised entirely in
- PL/pgSQL coding and
- configuration of PostgREST and NGINX.
Each API endpoint emits a JSON document assembled via PostgreSQL JSON functions, representing the domain entity in its current state.
The emitted JSON document is manipulated and presented to the next API endpoint as determined by the required state transition.
API Requests are authenticated via JSON Web Tokens (JWT).
- 2019 October 8 15:00 SAST
- 40 min
- South Africa 2019