Reducing boilerplate

[itsezc]

The goal for lucid is to replace traditional backends (whether they are monoliths or microservices – both have their pros and cons), they're difficult to build, maintain and scale.

After building several apps with lucid, we have made several observations which we hope will enable us to optimise the functionality that we offer and provide better abstractions for you so you write less code, after all less code is usually better.

Permissions
One of the areas where code is often repeated between models is when writing permissions, the most common behaviour is usually user access and for SaaS like apps allowing "groups" or "organisations" which have their own members with roles and permissions associated within.

For instance: a Github org, allows members to be a part of an org on an invitational basis, and there are “teams”, within said org that have access to different repositories.

Lucid can help make the syntax concise and unrepetitive.