I appreciate you taking the time to read the post and for providing valuable feedback on the product. As a developer, I understand the importance of being cautious when entering database credentials into any third-party software. Therefore, the focus when promoting the product is to clearly highlight the encryption mechanisms implemented.
Regarding future features: restoration, backup encryption and storage for pro level clients are planned in the short term.
This current version of the product is functionally basic. The mechanisms implemented for backups are mysqldump and pg_dump, respectively. The objective is to evaluate its viability and usefulness in the market, also considering open source and self-hosted alternatives. Importantly, in the short term, I do not anticipate having clients with overly large databases. However, if this situation changes, I will have to reconsider the backup methods.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi,
I appreciate you taking the time to read the post and for providing valuable feedback on the product. As a developer, I understand the importance of being cautious when entering database credentials into any third-party software. Therefore, the focus when promoting the product is to clearly highlight the encryption mechanisms implemented.
Regarding future features: restoration, backup encryption and storage for pro level clients are planned in the short term.
This current version of the product is functionally basic. The mechanisms implemented for backups are mysqldump and pg_dump, respectively. The objective is to evaluate its viability and usefulness in the market, also considering open source and self-hosted alternatives. Importantly, in the short term, I do not anticipate having clients with overly large databases. However, if this situation changes, I will have to reconsider the backup methods.