Investigate & Tech Spike capabilities and proposed implementation for API design in Phoenix framework (Elixir) and caching.

[nickscialli-usds]

On caching/pubsub:

• There's a good article by the creator of Elixir: You May Not Need Redis with Elixir.
  • Despite the title, I think he actually makes a good point about why we would want to use a separate caching solution like Redis: "if you have ephemeral data in Elixir, the odds are that you may not need Redis. However, if you need to persist or backup this state, then Redis or any other database will be handy."
  • The TL;DR is that, while Erlang/OTP does have some good caching/pubsub capabilities, we'll likely want a solution like Redis that's backed by a database/persistence (RDB+AOF) since we really can't afford to lose any data stored in the in-memory cache.

Still reading a bit more on this and will post updates