3 ms·

Is it unfair to think you're saying that a leaky abstraction is good?

• LunaSea 11y ago
  I think it depends on the case but my point is that if you hide to the developer the cost of that abstraction than you will get some surprises in performance later on. There are lots of reasons why an abstraction was written, ease of use being one of them but this also means that they don't always cover all bases (like performance). Which is alright if you (the developer) know about it. Thanks to GraphQL or Falcor I can most likely do something like "return me an object containing table1.colA, table2.colB, table3.colC, ...etc." very easily but it also means that I just asked for at least two joins. This can get really expensive if every developer on that project has the ability to do costly queries like this.
  • aljones 11y ago
    Falcor is intended to be used as a router to microservices, which could even be a REST api, not to database directly. A microservice would be between Falcor and the database. It isn't an ORM. It won't build a query. The services Falcor gets data from should have sensible limits that prevent unacceptable performance, whether you use them with Falcor or not.