Why Reorganize?
Our API has grown to include a number of services over the past year. It can become confusing to new developers to quickly grok which routes/class/services are responsible for which services. Let's do some serious reorganization to segment out these services into their own namespaces. As an added bonus, if we later wanted to extract some of these services as gems, this would put us in a much better place to do so.
API Version upgrade!
This will entail massively breaking changes to the API - so we should upgrade our version number. I realize our prod, beta, and alpha are the only consumers of this API, but it is still good practice and this will enable us to smoothly deploy to alpha, beta, and eventually prod.
Why Reorganize?
Our API has grown to include a number of services over the past year. It can become confusing to new developers to quickly grok which routes/class/services are responsible for which services. Let's do some serious reorganization to segment out these services into their own namespaces. As an added bonus, if we later wanted to extract some of these services as gems, this would put us in a much better place to do so.
API Version upgrade!
This will entail massively breaking changes to the API - so we should upgrade our version number. I realize our prod, beta, and alpha are the only consumers of this API, but it is still good practice and this will enable us to smoothly deploy to alpha, beta, and eventually prod.