I know this is subjective, but as experienced professionals, do you prefer a single-file larger solution or a several smaller file solution?
For example, let's say a service company wants a CRM/Scheduling/Service Order/Task Management solution. Would you build all of those elements into one database or several smaller departmental databases? Why? What would be the pros and cons to each method?
I've built both and tend to favor the "low hanging fruit" multiple database approach, but it largely depends on the scenario. I'm curious to gain some perspective from other devs on the topic.