Building a modular web application with python flask, Angular, and AWS : Part 6 Next Steps

Written by: Stefan Bradstreet

To everyone that has made it this far thank you very much for taking time to read my first several articles and getting acquainted with Flask and AWS and initially setting up Angular in the front end.

I have fought with myself many times on how to write this sixth article and setting the front end up for working with signing in users and dealing with sessions in the back-end and after several comments on the original Angular article and looking around I have deemed that this is not a great approach; especially considering this doesn’t leverage the Jinja template engine at all. After reading through several Flask books I have realized this is the wrong approach and it would be best to improve on my original implementation by ditching Angular and migrating to React.

By all means you can continue learning Angular 1 and have a fine web app if you work within the limitations of the framework to expand the users table and create a messages table but to stay relevant I will be pivoting the series.

Angular one’s  limitations exist with support of ES6 and the MVC architecture it uses is relatively more complicated then using the component design pattern of React to do back-end data-binding to update the dom in ‘real time’. A true component based implementation also increases re-usability in theory.  The series with take a shift to deep dive Flask and React using more of Python’s plug and play modules and automating the set up and deployment of web applications for quick use.

So while I may have taken a break along with a personal vacation, I am still very much active and inspired to continue teaching Python and web application related development!  Please support the blog by leaving a comment and selecting follow, or follow me on Twitter at @comsciu .  Your readership and interest helps drive the blog and is greatly appreciated.

 

Leave a Reply