Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple product list management from frontend #1590

Open
NimJay opened this issue Mar 7, 2023 · 1 comment
Open

Decouple product list management from frontend #1590

NimJay opened this issue Mar 7, 2023 · 1 comment
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@NimJay
Copy link
Collaborator

NimJay commented Mar 7, 2023

Describe request or inquiry

  • Today, modifying Online Boutique's list of products requires an update to the frontend.
  • See previous change to list of products here.
  • This is because the frontend hosts the images for all products (see /src/frontend/static/img/products folder).
  • Ideally, we would not have to update the frontend.
  • That is, product list management should be decoupled from frontend — in true microservice spirit.
  • Potential solutions:
    1. have the productcatalogservice publicly host product images,
    2. introduce a new microservices for publicly hosting product images,
    3. have the productcatalogservice upload images to a public-hosting service like Google Cloud Storage (GCS). This approach would be similar to Avocano (another GCP demo application). Avocano uploads product images to GCS buckets and makes the backend share the URLs of those images with the frontend as needed.

What purpose/environment will this feature serve?

  • This is part of a recent effort to make Online Boutique relate more to the ecommerce and retail industry.
  • An important takeaway (for users from the ecommerce/retail industry) inside should be: how to decouple product and inventory management from the rest of the app.
  • See Google-internal doc here for more info.
@NimJay NimJay added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Mar 7, 2023
@minherz
Copy link
Contributor

minherz commented Aug 28, 2023

Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants