On Wed, Jan 8, 2020 at 3:01 AM Ronit Mishra <ronnie94offic...@gmail.com> wrote:
> Hi Balaji, > > Here are a few things for you to take note down based on my experience. > > The simplest architecture is the best architecture. > > Be it *Apache *or *Nginx*, you're using *Django*'s wsgi services and > using *Bootstrap *for designing your layout. Probably with some storage > solution, either a database or remote servers/cloud, if you're storing file > physically. > > Things to observe: *Django *is the core of your stack. Its NOT just > backend but serves as your frontend as well (although for small scripting > uses, *HTML5*, *CSS/SCSS*, *JavaScript *is also used alongside *Django*) > You're using *Bootstrap *just for material designing. > > > Decoupling the services > > There is a different framework named "*Django Rest Framework*", which > works in the backend capacity to create *API*'s for your application. > In that case you'd preferably use something else for the frontend, like > *React*, *Angular *or *Vue*. They are nothing but frontend frameworks > based on JavaScript. > > *Please note that, you could still use Bootstrap to design the materials, > while using React, Angular or Vue as your frontend framework.* > > > The main idea behind destructuring the solution in 2-tier; an api builder > and a client end, is to decouple the two services. These two services > operating independently, can communicate with each other and establish > *Separation* *of C**oncerns (SoC) *architecture. Core logic or business > function resides in the backend and stored away from the frontend code.The > frontend, focuses only on the visual aspects and utilizes api endpoints to > display the data. > > > Using frontend framework is not mandatory. > > You're already achieving the desired result from your architecture, which > uses *Django* with plain old *JavaScript*. However, learning these > frameworks, will save you a lot of time while development, testing or > deployment your code. > > > More importantly.. > > If you're a web developer, I would strongly suggest you to go ahead and > pick one framework and start your journey. But if you're *NOT *a web > developer, and this happens to be an automation/service/solution in > addition to your main application, then you should skip these frameworks. > Probably work on making the architecture more resilient and fault tolerant. > > Also *PythonAnywhere *is not an industrial solution, so you might want to > consider *Heroku or* *DigitalOcean *or any other enterprise cloud > solution. > > All the best, > Ronnie > *Hey Ronnie * *i appreciate this detailed answer, balaji will get full about development* <https://about.me/sagarninave?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb> sagar ninave about.me/sagarninave <https://about.me/sagarninave?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb> -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAA6pdZ_U2xQKs0P2P-oAKg4VFtTKyq3eKcBeXONE%2BHdRyQQ0nQ%40mail.gmail.com.
