I'm developing a unified enterprise-grade Rust development framework as an alternative to Spring. The core idea is to hide all complexity within macros, borrowing from Spring CI/DI approach.
To allow Java programmers to migrate to Rust without any mental burden.
I need your suggestions and your requirements for various business scenarios. 
Not implementing the possibility for SQL injections would be a good start.
6 Likes
Injection isn't specifically bad things. It's actually a possibility to extend a functionality when it wasn't initially planned. I solve a security risk just sanitizing data entered in the system externally.
Regarding the framework, I think it's a good start. I implemented several frameworks in Java for web development and still use them As I see now, Spring looks similar to them them, so your Rust variant can be even better.
1 Like
I wonder what “externally” means. WRT this as a framework, I assume you mean the user of the framework. Given the context that this is enterprise grade, allowing user to handle sanitation and if fail to do so exposing company data isn't a good compromise.
Extension can be provided through side-channel such as raw SQL mode or the like.
1 Like
Data coming from the outside of the system, for example a supplier stock numbers. Users of the system as internal as external are also considered in the category.