3 ms·
The problem is that this tables are like "foreign" to the db, in a micro-service mindset (the worst anti-pattern to date!). That is a major complication. In D
by mamcx 6y ago
The problem is that this tables are like "foreign" to the db, in a micro-service mindset (the worst anti-pattern to date!).
That is a major complication.
In Django, this solve neatly, because I can point to my own table or easily integrate the ones of Django without much fuss. This turn all this in a non-issue.
- eropple 6y agoYes, they're foreign to your application's database. That's the point: by using these tools you're buying into a service-oriented architecture. What you are advocating is to collapse the service-oriented architecture into a "everybody parties on the database" architecture. These tools are very much invested in you not doing that. There already exist user-auth libraries for what you want and run inside your application itself.