- web team dictates
- feedback/criticism of API welcome
- fix in API rather than work around if possible
- WebUI using CaseAPI for 7.3 (rather than hitting sql directly)
- validate functionality and usability of API
- address tech debt & buggy areas of case
- increase WebUI performance
- 0 case bugs
- improve maintainability & extensibility of Case as a feature
- entirely based off of identity in Authorization header token
- relies on Auth Service for Authentication
- CaseAPI handles Authorization
- API calls that return lists will support paging
- this includes dateUpdated filters for more efficient polling
- can discuss other solutions, but this this is a minimum req
- shadow tables
- 3000+ stored proc
- raw rows in web indexer
- multiple caches & complex logic in WebAPI & WebUI to make usable
- new model
- no need for indexer
- should be able to delete a lot of code
- migration
- totally new feature
- API for initial feature set mostly done
- back and forth expected
- Not part of the API, unchanged for now
- Frank probably knows current state the best
- Do we need them?
- If caching is being discussed, always ask "Could the API do something to remove the need for a cache?".
CaseAPI + Web UI
By Chris Langager
