Necessary to learn React/ Angular with backend Django

[Balaji Shetty]

Hi

Currently i deployed application on pythonanywhere. It is online office file management system with around 100 users under 10 different department in hierarchical manner.

User and department may increase in future.

Entire application is developed in Django back end.

Used bootstrap for custom report generation.

question arises in My mind is

Is it Necessary to learn and implement in React/ Angular for front end.

Because I am comfortable with current implementation.

May I know what are gains i may get or what are the disadvantage i may suffer in future.

Kindly guide me to avoid future inconvenience.

--
Mr Shetty Balaji
Asst. Prof.
IT Department
SGGS I&T
Nanded. My. India

[Karan Mittal]

Hello friend,

In my opinion if it is working with current implementation you need not add any react or angular.

Learning perspective they are good but implementation of the same in your already working project may raise new errors. 

That's my opinion, feel free to incorporate them once you have learned and get the response to do so by your users. 

Regards, 

Karan Mittal

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAECSbOuN%2BBsvoGZ4nBA5D9batL9UAYQ4crZGWmaMxYMJQ5X1sQ%40mail.gmail.com.

[Gil Obradors]

My opinion,

If you want a great powerful user interface ( and experience) of the front end, yes, interesting to spend hours.

If the users won't appreciate it, no.

Other voice...

Good luck!

Missatge de Karan Mittal <karanshy...@gmail.com> del dia dt., 7 de gen. 2020 a les 19:38:

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAO24gqwBgRkr8LYhpHXS2A0o2i4Lcx1WdL%3DqnAuQPtOmtmnXvw%40mail.gmail.com.

[S D]

Hi Balaji,

You can convert your web app into a PWA to gain maximum benefit. Just look it up.

Data shows that PWAs are the way to go.

Kind regards,
- SD

[Ronit Mishra]

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 Concerns (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

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAO24gqwBgRkr8LYhpHXS2A0o2i4Lcx1WdL%3DqnAuQPtOmtmnXvw%40mail.gmail.com.

[sagar ninave]

On Wed, Jan 8, 2020 at 3:01 AM Ronit Mishra <ronnie94...@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 Concerns (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

sagar ninave about.me/sagarninave

[Integr@te System]

Hi Shetty,

You also consider your project serve local users, so unnecessary implement high interactive pages from internet clients. 

From online docs, you can learn any technique via small best practices and apply to your case with basic javascript knowledges or look at python libs, and then expand features as business change.

Dont forget systems behide when business move beyond, at least data.

Nice.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAO24gqwBgRkr8LYhpHXS2A0o2i4Lcx1WdL%3DqnAuQPtOmtmnXvw%40mail.gmail.com.

[Balaji Shetty]

Hello Dear Community

Thank you very much for your nice reply. Definitely your guidance will help me a lot.

To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAECSbOuN%2BBsvoGZ4nBA5D9batL9UAYQ4crZGWmaMxYMJQ5X1sQ%40mail.gmail.com.

--
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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAO24gqwBgRkr8LYhpHXS2A0o2i4Lcx1WdL%3DqnAuQPtOmtmnXvw%40mail.gmail.com.

--

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWpd7-Y7cV%3DG6UR1h_sPibr9gFmzBTQ0EDcTT7v0cDTWMg%40mail.gmail.com.