Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
After that, you're left with everything else in your application, much of which is interrelated on the data level. Using this repo as an example, you find that it has Accounts and then Blog as the primary namespaces (which make sense), which then leaves you with blog.ex which is a file containing a ton of database reading/writing/helper functions for all these different entities in the namespace (this is how the generators will also scaffold things, continuing to pile on the functions). It feel strange to me to have one giant file that forever grows proportional to the size of the namespace with so many concerns. Is it a good idea to split these things out (particularly when the ecto models aren't responsible for database queries in Pheonix) or am I just thinking about this the wrong way??