Note that there are some explanatory texts on larger screens.

plurals
  1. PODoes Django development provide a truly flexible 3 layer architecture?
    primarykey
    data
    text
    <p>A few weeks ago I asked the question <em>"Is a PHP, Python, PostgreSQL design suitable for a non-web business application?"</em> <a href="https://stackoverflow.com/questions/439759/is-a-php-python-postgresql-design-suitable-for-a-business-application">Is a PHP, Python, PostgreSQL design suitable for a business application?</a></p> <p>A lot of the answers recommended skipping the <strong>PHP</strong> piece and using <strong>Django</strong> to build the application. As I've explored Django, I've started to question one specific aspect of my goals and how Django comes into play for <strong>a non-web business application</strong>.</p> <p>Based on my understanding, Django would manage both the view and controller pieces and <strong>PostgreSQL</strong> or <strong>MySQL</strong> would handle the data. But my goal was to clearly separate the layers so that the database, domain logic, and presentation could each be changed without significantly affecting the others. It seems like I'm only separating the M from the VC layers with the Django solution.</p> <p>So, is it counterproductive for me to build the domain layer in <strong>Python</strong> with an <strong>SQL Alchemy/Elixir ORM tool</strong>, <strong>PostgreSQL</strong> for the database layer, and then still use <strong>Django</strong> or <strong>PHP</strong> for the presentation layer? Is this possible or pure insanity?</p> <p>Basically, I'd be looking at an architecture of <strong>Django/PHP > Python/SQLAlchemy > PostgreSQL/MySQL</strong>.</p> <p><em>Edit: Before the fanboys get mad at me for asking a question about Django, just realize: It's a question, not an accusation. If I knew the answer or had my own opinion, I wouldn't have asked!</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload