Making Improvements To My Sql Architecture

I needed to design an SQL architecture to store the various information. This is what I have came up with. Is there any SQL concepts I am missing that could drastically enhance my

Solution 1:

I would suggest replacing casting table with two tables - filmactor(having one row per film per actor) and filmdirector (having one row per film per director). Your casting table has director_id repeating for each row for a given film which is not needed (it is also not in 3NF). Also, it will not handle the scenario properly where there are more than one director on a film (improbable but not impossible).
Other than that the design looks fine to me.