Thanks For the feedback Aware & Everyone Else...
So in essence the Absolute nr one solution I suppose (In terms of Security & Performance) would be to implement both. I.e. Use LoggedInUser AND Protection rules. This way the Query Result Set can be made smaller BUT the protection rules protect against Hackers.
In terms of the Extraction of a single Tenant's Data... I would guess the easiest would then be to create a Relationship From every single table to the Tenant so that one doesn't have to struggle with tons of JOINS to get all the data.
Neway, thanks again for all the new videos and looking forward to more to come. I think we as users should Also start making these so that we can build up a massive portfolio of material, tips & tricks, that will help New users to get going a lot quicker and so growing the product and user base. Also this will make the learning cycle easier if one wants to appoint a new developer in the team. It's quite a struggle to find the right person and to get them comfortable with the tool fast enough so that they can start taking some of the load.
Me and Werner are planning to do one on Exposing JSON services for Consumption specifically by Native Android apps since we've done a TON of these now. Hope to get that out to you guys in the next month or 2.