[Django]-Django from Java developer perspective

by

4👍

✅

Django on the other hand looks a little bit procedural, you map requests in a file, write your handlers in another, write your domain classes in another …

As a Java developer, how is this any different than a traditional Java MVC pattern? It’s just different names: Django uses “view” for what is traditionally (in Java-land) called a Controller, “template” for View, etc.

Don’t you have domain classes in your Java application as well?

In Java-land, when you have an MVC webapp, you have the same sort of splitting of logic:

  • You write the request-handling logic in your Controller
  • You represent the “domain” in your Model/domain classes
  • You write the display logic in your view templates/classes

I’m having a hard time understanding what you think is different about Django beyond the names.

👤matt b

Leave a comment