KaloyanYosifov
commented
3 months ago Reminders implementation
Dependencies
- Diesel-rs - ORM library with DB connection drivers support and CLI for migrations
- Pros: We do not create something custom, easy to use and migrations support
- Cons: We depend on the library to be maintained, can get bloated and increases complexity of the project (to understand the pieces)
New modules
- Schema - automatically kept up to date by diesel, based on the migrations
- Models:
- Reminder
- Create Reminder (acts like a DTO, maybe we will have a dto instead of exposing the create model)
- DTOs - (if we decide to use a dto, instead of doing create model)
- DB Connection - used to set the database we are going to use for the application.
- Service - CRUD encapsalation for a model.
Questions
Why a service for the actions towards a model?
I initially though we could go with an Actions/Query seperation (Separate actions from reading), but since we might make everything on a macro, it will not provide a big benefit to separate them here, as Rust's encapsulation of a module is good enough. The service will handle both the do and the read operations, which allos us to go to one module to understand what we can do to a model
Do we need DTO's?
Probably. My idea for this is to not expose the "model's" functionality and instead just have a PORS (Plain Old Rust Structure, inspired by POJO) that just holds the data and it is agnostic to a database.
The design might change, this is just my initial brainstorming on the topic
As a user I would like to have a reminders view, so that I can set reminders to not forget thins :D
Diesel-rs looks like a good ORM and it provides support for migrations