You are creating a new instance of SQLAlchemy on every concern.

[alesanchezr]

I know we are doing microservices, but still I think all the configurations for the Flask database should be in just one place, that way we can import it and declare our models on every model.py.

The current way could lead to bugs because maybe I forget to copy and paste the configuration to every modal.py

flask-microservices-boilerplate/api/user/model.py

Line 3 in 297a623

db = SQLAlchemy()

[jferragut]

@alesanchezr I feel like we should lean on cloud DB. I am adding a firebase example. In that example I am creating a class to define the data model but then I use the firestore to save the data. I don't actually instantiate this way anymore. Also, I am removing SQLAlchemy due to this approach.

Please let me know if you see another reason to do it this way instead of how I mentioned.

I am trying for this not to be too opinionated on how things should be done, rather it should be a starting point for your project and allow flexibility.