I'm just learning about database design and I'm working on a contact management app for work. I'm reviewing schemas online for thoughts on best practices when I found the following design:

Contacts and Products

It looks simple but then the Communications table has three foreign keys that's always been a no-no. In the world of "we need something now" is this a workable schema, or is there a better implementation?

Why? Actually I can see six but that doesn't make it "wrong".

If contacts is what you are looking for then take a look at Fowler's party data model:

A Universal Person and Organization Data Model