In traditional APIs, it is hardwired into the way each API is built. Each experience API made the right call to a set of domain APIs (scattered), and then combined the results (gathered) into one.īut scattering/gathering is not easy. Netflix had “domain APIs” that reflected how backends viewed and surfaced their data, and they had “experience APIs” that reflected how applications wanted to access the data. I had first heard this concept in hearing how Netflix talked about their API tier, in particular from Dan Jacobsen, who is now at the New York Times. In this paper, we will address the latter, we have previously written articles about the former. The query that you submit is scattered to multiple backend databases, and the results are gathered to present as if they were coming from one centralized system. Second, equally importantly, many databases know how to federate, meaning that if your data is scattered across two database systems, then one can execute a query against both as if it was coming from one.APIs, on the other hand, have mostly been created programmatically. ![]() You follow that principle whether you are creating data or querying for it. That means you tell the database what to do, not how to do it. The first is that databases operate declaratively.Anant is the founder and CEO of StepZen, a startup with a new approach for simplifying the way developers access the data they need to power digital experiences.
0 Comments
Leave a Reply. |