brendan/brendan-ch.github.io
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove the design/implementation section of Interchange

Browse Source 
(may publish later elsewhere)
This commit is contained in:
Brendan Chen
2026-02-12 22:23:13 -08:00
parent 1f9ae01c91
commit 43bc383bcc
1 changed files with 0 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
projects/interchange/index.md
View File

@@ -14,15 +14,3 @@ GraphQL, with Redis as a primary storage mechanism.
[Join the TestFlight](https://testflight.apple.com/join/HbuHfUgW){: .secondary-action }
[Website](https://interchange.bchen.dev/){: .secondary-action }
{: .horizontal-wrapper }
## Design and implementation
The server is built using Node.js. I designed a basic GraphQL schema and
used [Apollo's GraphQL implementation](https://www.apollographql.com/docs/apollo-server/getting-started) to bring it to life.
In GraphQL, data is represented using a schema, which is then fulfilled with
resolvers defined in code. Each resolver function gets some information like the
parent object, arguments, and a server-defined shared context. Seeing the dependency injection that you could do with this context, I decided on an object-oriented approach consisting of **loaders**, **repositories**, and **systems**. Loaders load data from an external source, repositories store data, and systems are composed from a set of both loaders and repositories.
I then applied an event-driven pattern to implement the iOS notification sender, listening to updates on the shuttle repository. I would eventually reuse this pattern to implement an ETA prediction system that could run independently of an external data source.