Marketplace/Mobile Optimized Websites/engineering: Difference between revisions
(Created page with "The Marketplace was built with a single database table holding all our apps. The easiest way to add another type would be to add a column called `type` or add another table a...") |
mNo edit summary |
||
| Line 4: | Line 4: | ||
[[File:mkt_mow.png]] | [[File:mkt_mow.png]] | ||
In this proposal there is no UI for managing the websites stored in AWS. It will all be done via APIs. This scales well with the phased rollout/review plan since APIs will mean minimal implementation time. | |||
=== Open Questions === | |||
* If we add ratings/reviews where do we store those? | |||
* If we add owners or a management UI, where does it live? | |||
Revision as of 19:14, 18 February 2015
The Marketplace was built with a single database table holding all our apps. The easiest way to add another type would be to add a column called `type` or add another table and change our code logic to look at both. Past experience (AMO) shows that this can lead to unnecessary complexity around queries and templates, especially when the data hops through several hoops (like Elastic Search) to get to where it is going.
We emphasize the Marketplace being 100% API based on the front-end -- this proposal brings those same benefits to the backend as well.
In this proposal there is no UI for managing the websites stored in AWS. It will all be done via APIs. This scales well with the phased rollout/review plan since APIs will mean minimal implementation time.
Open Questions
- If we add ratings/reviews where do we store those?
- If we add owners or a management UI, where does it live?