Thread

1. efromvt · 1790794752 · focus · HN ↗

   I’m a big fan of the strict naming as an abstraction above tables and reuse as blend key approach, it also greatly simplifies aggregate resolution like you have. (Landed on the same abstraction level when building a semantic model personally).

   Lots of 404s on the docs pages - might be worth an audit of links?

   1. ajoski9 · 1790863673 · focus · HN ↗

      Thanks for the heads up. I do have a specific question on your implementation. We were thinking about launching a semantic layer as a service api. You post your model and we give you fast query generation. You can then use this in your own tools. Benefits are a fast expressive semantic layer, model hosted, and your actual data stays behind your firewall. What do you think of this?

      1. efromvt · 1791065837 · focus · HN ↗

         I think a service that simplifies things enough can get people to pay for it, but semantic layer is tough because you often also do want to encode sensitive information, you need to minimize latency, and it’s in the critical path of a bunch of other stuff. You’d need to differentiate quite a bit vs a local hosted option with more flexibility. That’s why semantic layer vendors are often semantic layer ++ ; you want to hook into an ecosystem to get sticky. Doesn’t mean it won’t work!

Unofficial Hacker News client; not affiliated with Y Combinator.