SPIKE: Architecture options for Riff Server

[adonahue]

As a PM, I would like to restructure the way data is stored in Riff Server, so that I can build more sophisticated metrics, which are currently inhibited by the data access and processing that would be required with our current server.

As a developer, there are many things I would like to fix in Riff server, so that future code development, data storage, and data processing will be easier.

This spike is to allocate time for the dev team to explore ways in which we might enhance Riff Server. The goal of this spike is to provide a cost / benefit analysis of making changes to the server, as information for the business in order to sequence and prioritize work.

• Document the problems of Riff Server
• Explain the consequences of those problems
• Possible ways to mitigate those problems (e.g. refactor, rebuild, augment)
• High-level effort for each piece of work (e.g. easy, medium, hard, no idea)

Acceptance Criteria The spike should cover:

• [ ] A meeting with Dev & Beth with other team members optional.
• [ ] A summary doc and team meeting to present the findings for the bullet points above.

[jaedoucette]

What's wanted here is a set of options for how we could proceed with different kinds of refactors or middleware construction, or scrap and total redesign.

[juliariffgit]

Meeting to articulate: Problems with server High-level possible new solutions