TOTAL ISSUES 220
AUTOMATIC ISSUES 220
NEEDS REVIEW 160
GUIDED ISSUES 0
But, the fact that I don't a perfect solution right off the bat is not a reason to stop exploring!
Also: ALL CAPS.
No, those are not about responsibility. Is a river responsible for someone drowning in it?
The incorrect hyphen is just irritating as well.
> Relational database seem to be a crazily overengineered solution in search of a problem
Why would an answer to that need to mention Kafka consumers?
This is the part I was responding to.
I consider this a form of gatekeeping of advice on using Kafka.
> The ORM was a natural culprit: it’s easy to see that many ORMs will make use of object introspection to build SQL statements, hydrate results, or both. Gorm’s memory footprint is extreme although sadly not uncommon. Bridge started with Python on the backend and we used Django’s ORM to interact with the database which had similar problems.
I believe these are both active record ORMs, which are not as good for various reasons (including default memory usage) as good data mappers such as SQLAlchemy and Hibernate.
As for where enums etc are "mastered" - this is still a decision to make with or without ORMs.
I think the main tricky bit of ORMs is that objects are trees and relations are graphs; this causes problems. Not so much anything about encapsulation etc.
But yeah, parallel programming is easy to explain with Factorio.