On Nexuses: An underrecognised utility in computing (2015)

I call these branching libraries.

Definition: Use one kind of thing as another kind of thing.

Given X {scenario,state,message,event,format} do Y

Generics gets us some of the way to what we want.

https://github.com/samsquire/ideas#48-branching-libraries

Using a database as a spreadsheet or a spreadsheet as a database, using a spreadsheet as a functional programming language or bash pipeline editor with each cell being the output of that pipeline step. Or reactive programming with spreadsheets.

I am trying to solve the expression problem. To introduce a new thing into an old thing you typically need to implement hundreds of functions on an interface.

A nexus that composes is what the industry needs

interesting idea. databases/warehouses are one form of nexus then. not a platform, but still a nexus. as i went into data engineering I discovered that a lot of people are using ETL tools (like Fivetran and Airbyte where i work) to move data out from saas data silos into a warehouse basically so they dont have to figure out each API themselves. from there multiple teams can rely on the same data without any coordination. i think its a very interesting pattern that basically arises out of CAP theorem (and the pesky fact that APIs are not standardized; SQL is a much better "API" than most APIs)

That is the first time I've heard Nexus used in that particular way. Is it custom to the author or a widely accepted definition?

"Nexus as pub-sub queue" will be the next fad

(2015)