When using the live Creator, what is the trade off of using just views over tables, when designing an API that utilises sub resources, from a performance point of view. i.e. views loose relationships (foreign keys) and indexes ... what impact does this have if any? Currently we experiencing very poor performances, but its due to how CA handles the multi level API data structures. In addition filtering is handled very poorly when filtering by a sub resource where the primary resource doesn't filter as well - so these all seem Independent from each other and results in multiple DB calls being made to create 1 JSON object, which is inefficient.