Pods is very good for relational data. While you could always use the excellent posts-2-posts plugin by scribu (FYI: a core WP dev) if you choose to use CPTs (Custom Post Types) instead of Pods, what makes Pods better (IMO) than CPTs is that it abstracts the data into its own table (Of course, arguments against this can also be made). Pods offers significant performance gains when dealing with large data sets. There was a post somewhere by Scott Kingsley Clark, the lead Pods developer, with some really impressive performance tests stats, but I can't seem to be able to find it now. Anyway, the Pods API is quite robust and with 2.x (released yesterday) it has got more polished than before. With 2.x you could even use Pods to maintain CPTs and other WP types and abstract them into their own table. How about that! You may want to refer to the points made here by Scott: http://wrangl.com/pods-vs-custom-post-types
I am currently working on a site where I have used Pods to set up a database for a non-profit that offers various levels of language classes. So the database contains tables of people, teachers, students, locations, classes, class-levels, class-posts, etc. Various fields from these tables are interlinked using the relationship field type. Like I said in the beginning, if you have relational data, Pods is an excellent choice. However, do keep in mind that you would have to do some programming to really leverage the potential of Pods. Also, things like RSS feeds, sitemap integration, etc. have to be coded up. I am planning to release my code for a lot of these things once I am done with this ongoing project. Hopefully, that will drive more people to adopt Pods.
The devs maintaining Pods are quite serious about their work and in the limited time I have used Pods I have found them responsive to questions, bug reports, etc. While being open-source, there is a road-map for Pods going forward and I highly recommend it for anyone looking to use WordPress with complex relational data.