This is the part-2 of the Alternate Middleware Option series....
After all the analysis and evaluation we decided to choose PYTHON as it was fitting best in our point of view.
Now our next step was to build a web application or a desktop application or a mobile application or any such thing that would support us in our idea of choosing Python.
We then decided to create a website as a POC (proof of concept).
Now, we had this job of creating a website in Python, so we again started to checkout for the ways to do this. And then we came across the two most popular web frameworks; the Django Web Framework and the Flask Framework.
We again had to pick one among these two...
When we started trying to analyze in order to make a decision in this case, we had these below observations:
1) Django offered us the conventional project structure, whereas Flask comes with an arbitrary project structure.
2) Django use specific names like, for URL (urls.py), models, views etc. This simplifies adding new people to the project as codebase navigation is easy for them.
3) Django was created for the rapid development of the complex web apps. Developers have all the tools they need to implement and develop; easy, scalable, reliable and maintainable web apps.
4) Django has huge active developer community. There is so much useful content in public domains where as Flask has comparatively smaller community than that of Django.
So, after analyzing the above observations, we made a decision of choosing the Django Web Framework.
Top comments (0)