Updates. By Jeff Kreeftmeijer

Replying to twitter.com/jvanbaarsen/status/1084162402843848704

Contexts provide the API to interact with your schemas to keep knowledge about your repository out of the rest of your app.

While they can group functions for multiple schemas together (like in the Accounts example), you’re encouraged to start with one context per schema if it’s not immediately clear what the groups could be.

For now, I’d call the context for the Recipe schema “Recipes”. Eventually, that context might manage both recipe and ingredient data, and you could have an Accounts context for handling users and their credentials, for example.