Recently I wrote about mocking auth in CAP for a rapid local-first development loop that allows you to embrace auth design rather than defer it to later. In development mode, unless otherwise stated (i.e. unless you add appropriate annotations such as @readonly, @requires or @restrict), all resources are accessible...

Book Overflow is "a long-form discussion podcast for software engineers" and one of the shows to which I'm subscribed. The recent episode 118 is one in the series where Carter and Nathan discuss the book Learning Domain-Driven Design: Aligning Software Architecture and Business Strategy by Vlad Khononov. I listened...

This post is one of a series on local-first development with CAP Node.js. Everything is an event In Five reasons to use CAP, we see that everything is an event. Whether synchronous, such as via HTTP requests and responses for OData operations, or asynchronous, where messages are emitted and received for decoupled...

This post is one of a series on local-first development with CAP Node.js. Calesi and mocking remote services In the context of CAP-Level Service Integration (aka "Calesi") we can mash up remote and local services, and in the full spirit of CAP generally, run everything in airplane mode, i.e. fully locally. Working...

This post is one of a series on local-first development with CAP Node.js. The mocked authentication strategy The Authentication Strategies section of the Node.js Security topic in Capire explains the different strategies available, and the "mocked" strategy comes with pre-defined users that can be used, with their...

This post is one of a series on local-first development with CAP Node.js. Initial, test and sample data - terminology Mocking data is likely the most common and useful of the various local-first development mechanisms that provide mock facilities. Before we start digging in, it's worth spending a minute on...

This post is related to a talk I'm putting together: Local-first development with CAP Node.js - mock all the things! As developers we need to be free of distractions plus a tight and speedy development loop. But definitely not at the expense of ignoring or postponing important design decisions. CAP's mocking...

This series post is related to a talk I'm putting together: Local-first development with CAP Node.js - mock all the things! As developers we need to be free of distractions plus a tight and speedy development loop. But definitely not at the expense of ignoring or postponing important design decisions. CAP's mocking...

See the series post for an overview of all the episodes. Introduction 00:00 Introduction and recap. 05:47 Patrice takes over and looks at the syntax diagram in the CXL topic of Capire and the specific path expression diagram. He remarks that one of the cool things about path expressions is that you can chain...

See the series post for an overview of all the episodes. Introduction 00:00 Introduction and recap from last time. 06:55 Patrice jumps back in and visits the CXL documentation in Capire, which already by this point has even been updated and improved. He also briefly runs over some of the expressions and concepts...

See the series post for an overview of all the episodes. Introduction 00:00 Introduction and recap from last time. 07:00 Patrice revisits the syntax diagram and starts to explain the insignificant-looking but very significant (in terms of power and utility) "ref" box in that diagram, which is the start of our...

See the series post for an overview of all the episodes. Introduction 00:00 Introduction. 03:12 Patrice confirms that the constraints that we looked at in the previous part are checked in an "after" phase handler. Revisiting core CXL building blocks 05:55 Patrice jumps into the cds REPL to revisit some of the CXL...