Jorg Thuijls
@_jorgt
jorg@dalraesolutions.com.au
- Thanks for the invite
- Background and interest in tech
- Several types of innovation
- This innovation is more about using existing technology in creative ways
- SAP's new development framework
- Most frameworks do API, or ORM but not both.
- CAP generates DB and API from same definitions, and deals with delta's
- CAP Core goes open source
- CAP Core AFAIK will include the Postgres plugin by default
- Bit of firebase history
- Bit of Supabase history
- How it works
- Postgres
- API from all public tables
- Security definers
- Walkthrough of supabase dashboard
- Explain SB local development
- Show CLI and Docker
- Chats, so messages and channels
- I ran cds init, supabase init
- Installed supabase, cds-pg
- Show CAP project
- Show package.json, vcap-services
- Show the schema and the service
- Show INDEX file, show successful call to $metadata
- Show
signInfunction andonAuthChangedfunction - Demonstrate what happens, click inbucket link
- Show local storage and cookies
- Show cookie parser, log cookie in middleware
- Show middleware with supabase verification, and log user object
- Show
lib/authand use user object to create a CDS USER
- Show signout function in index, show cookie clearing in CDS
- Log out and show the 401
- Log back in
- Show snippet for subscription
- Call
createMessage - Show web socket throughput
- Show database entry
- CAP can use Postgres
- There's overlap
- Supabase does not do migrations as well (there's a CLI)
- Postgres policies can be tricky to set up and debug
- CAP does not have persistence
- Both generate a very usable API. One does ODATA and GraphQL, the other JSON and GraphQL