The said project is an enterprise accounting (book keeping ) system.
It is not mere dynamic content such as that served by news rooms (the
very foundation of Django's origin ).
It is going to be lot of dynamic views which actually have to
conditionally serve ad-hock dynamic data.
On Sunday, October 11, 2015 at 10:33:03 PM UTC-5, krmane wrote:The said project is an enterprise accounting (book keeping ) system.
It is not mere dynamic content such as that served by news rooms (the
very foundation of Django's origin ).
It is going to be lot of dynamic views which actually have to
conditionally serve ad-hock dynamic data.We're doing the equivalent of an ERP system in django.
The django backend works great, and has handled probably more complex processing than you will do. Or at least, very complex, like event-driven MRP. It also does multi-party accounting.
Main problem we have is that complex pages with lots of django forms get way too slow. We plan to use django-restframework to create an API which will be consumed by something like React in the browser.
We use the django ORM, not sqlalchemy, but that would probably just make it all better.
--
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 post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c4d38614-621c-4cc2-ad74-2e4744725fc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We use the django ORM, not sqlalchemy, but that would probably just make it all better.
> The said project is an enterprise accounting (book keeping ) system.
> It is not mere dynamic content such as that served by news rooms (the very foundation of Django's origin ).
> It is going to be lot of dynamic views which actually have to conditionally serve ad-hock dynamic data.
As long as you can coerce the data into Django models (preferred), Python objects/dicts/lists, or have some function that returns the data in a sane serialized manner such as JSON/XML, that shouldn't be an issue. That's pretty much how all web apps work.
> It will also be used at point of sails counters for example in trade fairs and malls.
Here is where you'll run into trouble. PoS systems usually need to be able to run in a standalone mode due to a lack of connectivity. Django is not meant to be run directly on the client side (although I suppose it could be). Without connectivity back to the Django server, the clients need some way to store transactions locally and upload them later. A web application is not ideal in this scenario. You would need to develop a local PoS app (perhaps in Python directly) that knows how to communicate with Django as connectivity is available, usually via an API that you would write in Django that the app knows how to use.
You also need to be careful with the data that is traversing your system. Not sure what country you are in, but in the US, PoS systems are required to adhere to strict guidelines when accepting payments, even if it isn't stored within your system. If any sort of electronic payment card hits your app, you're probably subject to those regulations. Check with your legal and information security team before accepting payments.
> So is Django good enough for such development?
Yes and no for the reasons above.
> We are used to using sqlalchemy and would want to continue the same for ORM.
I believe there is 3rd party support for SQLAlchemy as a plugin for Django, but not officially out of the box. I'm not familiar with any packages to provide further comment, but they definitely exist.
> Happy hacking.
> Krishnakant
>
That's the last thing you want to say around a PoS system. :-P
If you have doubts, I would recommend you run through the tutorial and try it out yourself to get a better feel for its capabilities.
-James
--I see, I am sorry I could not read it properly.
Sqlalchemy is more performant? In what way? Do you have any reference or this was from personal experience?
--
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 post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/561C2FEF.8030800%40gmail.com.
Sqlalchemy is more performant? In what way? Do you have any reference or this was from personal experience?
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6tLcxawEHaSAvGsaUBpKDEq2O%2BWHZ-KoTPqtVsbuhUZs7w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/561C6B73.4090301%40gmail.com.