One of the goals of the framework is to be "batteries included" but I think you should be able to have more flexibility in what you want so you want so you are not carrying around a lot of extra dependencies for features you don't want or use. Obviously plugins would be the way you should be able to add those in. Features that should probably be plugins are:
The event system
The RBAC
That said I don't have any plans on supporting other dbs besides Mongo, at least not for a while. I think one of the reasons you would come to this framework is that you want Mongo to be a first-class citizen
We have a fair amount of dependencies already and I think we should try to keep this list very small and internal
For example when you bootstrap an Adonis project this is your package.json:
Which is a much greater spread. I think Kafka especially is a pretty big extra burden but I have a separate ticket to move that event system to be backed by Redis pubsub
One of the goals of the framework is to be "batteries included" but I think you should be able to have more flexibility in what you want so you want so you are not carrying around a lot of extra dependencies for features you don't want or use. Obviously plugins would be the way you should be able to add those in. Features that should probably be plugins are:
That said I don't have any plans on supporting other dbs besides Mongo, at least not for a while. I think one of the reasons you would come to this framework is that you want Mongo to be a first-class citizen
We have a fair amount of dependencies already and I think we should try to keep this list very small and internal
For example when you bootstrap an Adonis project this is your package.json:
You are just getting their own core packages plus database support
Ours looks like:
Which is a much greater spread. I think Kafka especially is a pretty big extra burden but I have a separate ticket to move that event system to be backed by Redis pubsub