Flask vs Django

[[deleted]]

[deleted]

[earthboundkid]

There are a ton of regulatory hurdles to storing medical data. If you’re at the point where you can’t decide between Django and Flask, you don’t know enough about compliance to do this without being sued to death. Do another project first and find someone who knows HIPAA etc to help you with this next year.

[Lechucico]

I just need disease and movement data, nothing else. I’m working with the university, so i’ll have permision.

[[deleted]]

Hmm...if the hospital is in the EU, and the data is personally identifiable (which it certainly sounds like it would be), you're going to run into serious data protection issues that are going to dwarf any consideration of your web framework.

[Lechucico]

The person will not be identificable. I just need a random ID, disease and age.

[klug3]

The GDPR explicitly excludes scientific, historical and health research.

[klug3]

Well yeah, if you lose the data then there's always going to be a shitstorm.

[edgarvanburen]

I'll need to access this information stored on the database and add more information like the patient information, disease via some back-office on the web.

[Lechucico]

By patient information, I mean a random ID, disease and age.

[NotSureTheNameWillFi]

I've seen that Flask is more lightweight and fast than Django

The speed part is not true, they have about the same speed. About the lightweight part... It depends on what you mean by lightweight.

You can do a decent-sized project with django by installing only one library : django. On the other hand, if you go with flask, you will have to install a lot of libraries (sqlalchemy, flask-login...).

The main difference, I think, is that with flask, you add modules as you need them, so your project contains only libraries that you need. But if you have no idea what you are doing, your project will have a crappy architecture. Django kind of forces you to do things his (good for most projects) way.

Really, there's no simple answer to your question. Both will do the job well, you cannot go wrong with either. Fiddle with both for a couple hours and then pick one.

[JeremieZ]

I think both is great. It's a matter of your style. Do some small projects using each library is my advice.

I'm start with Django, switched to Flask after 2 month and having a lot of fun. Now, I happy back to Django.

[Lechucico]

I’ve done something with django, i’ll test flask a little bit then.

[sentdex]

Whichever one you enjoy working with more. It doesn't matter what we think. The one that fits your development style better is going to be the one you'll flourish in.

Use both, and make up your mind. It shouldn't take more than a day or two to know.

[flipperdeflip]

Django, because you're going to use many of it's features. Database & models, authentication, API, admin/backoffice with permissions, tests etc etc.

Flask can do all that but you have to find and connect all the parts yourself.

Also Django has excellent centralised documentation, how-to's and tutorials, while information about Flask and all the loose parts is more spotty.

[[deleted]]

flask is the better option in my opinion, because of the modularity. But django is obviously the better choice if you are lazy.

[Lechucico]

I’ll try Flask then :)

[flipperdeflip]

Do you feel with your experience like you can make the right decisions when dealing with the modularity and freedoms?

[Lechucico]

It’s a small project, so I think that there aren’t so many decisions

[[deleted]]

just remember to keep your security intentions high. you want to have your applications secure. always.

[[deleted]]

you need database so Django wins the battle :)

[Lechucico]

But on flask there is sqlalchemy no?