All associated data in one database or split into multiple databases?
I'm developing an asset tracking app. An asset consists of an arbitrary number of attributes. It also has file attachments and notes. I broke the attributes, attachments and notes out into separate databases, but it makes the program logic a little more complex. I'm wondering if the performance gains by using separate databases that I'm picturing in my mind (with no real data to back them up) are really much better than just storing all of the objects in an assets database and giving them a 'type' field to differentiate them?