I will just add that you should pay attention to this note:
Both solutions are valid but both require have collection to be loaded. This is very inefficient as you have to load all necessary data for each item in collection means name of pub, location, date, happy hours … to be able filter these. if you have a few (>200) you can be be fine but when you start adding more and you will need to first load 500+ or 1000+ your clients will have slow response experience on first load → that is bad.
In real world you make request to server to get from server only data you need . WF doesn’t offer this approach yet directly in WF, but WF has Webflow-api that provides some functionality you need.
There is another but least useful option and it is use of 3d-party paid service as Make to achieve this. Anyway, there is more ways how to but… Too much hassle for simple fetch request.
Probably the easiest for you will be @memetican option and add “LOADING DATA” loader on firs load when loading tons of data to let clients know why they have to wait. 
| Category | Verdict |
|---|---|
| Visual editing |  Best-in-class |
| CMS for small sites | Fine |
| CMS for dev workflows |  Painful |
| Dynamic filtering, API, logic | Not dev-friendly |
| Safe token-based API use | Still needs external backend/proxy |