Pros and Cons for inventory future

## Purpose

We want to support inventory.data.gov long term, but we're not sure how to do that.

Given above architectural design decisions, conducting pros/cons list and research is needed to provide factual knowledge on future steps.

2 days of effort has been allocated and once compete, findings will be demonstrated and specific future actions will be decided.

### Acceptance Criteria

[ACs should be clearly demo-able/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]

- [ ] GIVEN a thorough analysis is completed \
WHEN 2 days expires\
THEN pros and cons list is showcased with time and value estimates \
AND architectural decision is made \
AND design and develop tickets are created

### Background

Stay with CKAN inventory, or move to custom application/service/tool model?

### Sketch

We did this analysis with CKAN for catalog, but the features and tools of inventory are much different. Need complete analysis before deciding path forward.