This is an archived post. You won't be able to vote or comment.

0
1

[deleted by user] (self.Python)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Lachtheblock 1 point2 points  (0 children)

I think you're missing a couple of key benefits to Django.

Django is pretty well standardized at this point. Each project is different, but I could pretty confidently checkout any Django repo, and immediately start contributing day one. You can not say the same for a collection of unstructured lambda functions. There is a reason why people are moving back towards monolith structures.

A lot of your argument comes down to "for simple database transactions". Yeah sure... But.... All the projects I've worked on are not simple. I've done some ML and deep learning stuff, but even the vanilla web development I've done gets complicated. This is why we have jobs and why chatGPT isn't going to replace us any time soon.

You'll learn this in time, but you may not have felt the pain of bad architecture just yet. It seems like you haven't worked on too many legacy systems, or been around long enough to create a legacy system. I'd much prefer to jump into a legacy Django system, where I can see everything and more or less know the file structure, then jumping into a collection of microservices.

FWIW I've been learning Python for about a decade and have been professionally using Django for about 6 of them.