Micha Mailänder

Fauna is a serverless database where you store data as JSON. Also, you have build in a HTTP GraphQL interface with a full authentication & authorization layer. That means you can skip your Backend and call it directly from the Frontend. With the power, that you can write data transformation function within Fauna with her own language called FQL, we're getting a blazing fast application.

Also, Fauna takes care about scaling and backups (All data are sharded on three different locations on the globe). That means we can fully focus on writing business logic and don't have to worry anymore about infrastructure.

You can give ClientDB a try. It simplifies storing data local, and it takes care about syncing it regularly to your remote data storage.

Advantages:

• It's cheap, because you don't have to send a write request to your database every moment. (And it's open source)
• If the user looses internet, it will sync up simply again at the moment he has internet again
• You can implement an instant experience, because you don't have to wait for database feedback e.g. saving data (Not so relevant for your Use case, but maybe overall interesting to know.)

Downside:

• You have an additional layer, that you have to maintain.

If these three are your options, I would recommend going with Auth0. They have all functionality available as developer API (Okta e.g. not) so you can manage your instance with Infrastructure as code and can also easily add functionalities relatively easily with the API. They are also really powerful if we're talking about ABAC (Attribute based access control). You can also enrich your access token with custom claims from your MongoDB, that can be probably really useful, as you said that you're dealing with multi tenancy.

We're using Auth0 in combination with Fauna Fauna is a database, so it would challenge you're mongodb. But Faunadb is the first database that implemented a full end user ABAC system directly in the database. (And also a lot easier than the ABAC systems from Okta or Auth0). This helps us, to use Auth0 only as identity platform and doing all the authorization with enriched claims over Fauna. With that you can skip in a lot of the cases you're backend, and you can request directly from the frontend your database (Blazing fast). Also, you can replace in some years Auth0 a lot easier with some upcoming cheaper (Auth0 was bought by Okta for a hilarious price) and "easy to use" passwordless identity provider like Passage.id

We're using Bit by our own.

You can develop UI components in isolation for Angular, test it, document it and deploy it also as standalone app. (Check out Bit Aspects https://bit.dev/aspects)

e.g. a Button: https://bit.cloud/myliang/fish-ui/button You see there the code for different frameworks like Vue, React and Angular. And you see there is also a live preview. So you could also change the code for testing purposes directly in the browser, and see how it changes.

Furthermore, Bit is not stopping there. With Bit you can build your whole Application as components (Including Backend - currently only Node.js, but support is growing), that you compose to a standalone App (https://bit.dev/docs/apps/apps-overview/). They're currently working on something called RippleCI, that will take the headache of integrating and testing components between different teams. Given you have a component "Button", and this component will be used in another Component "Card". If you change something in "Button", Ripple CI will run your tests for "Button" and if the tests passing, it will send a PR to your repository to upgrade the dependency "Button" in your component "Card". (Comparable to Renovate, but smarter) With that, you can enable true component driven design with independent developer and teams.

If you go on bit.cloud you see on the top left a search field. With that, you can search all open source components existing on Bit. That way you can also check out, how it could look like for other components. The company Bit has also shared all their components as open source. So you can see, how they use Bit by their own: https://bit.cloud/teambit