Skip to content

๐Ÿ” Product-storage service, work on gRPC. Client sends the URL to download products, and requests the result. The server transfer request to a third-party resource for .csv-file uploading and saves the products to own database.

License

Notifications You must be signed in to change notification settings

p12s/product-store

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

9 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Product store

Product store. Task description is here

๐Ÿ”ฅ Run

Download:

git clone https://github.com/p12s/product-store.git && cd product-store
mv server/.env.example server/.env
mv client/.env.example client/.env

docker-compose up --build

Stop:

docker-compose down

What is going on there

What does the client do:

  • sending address to download products (for example, http://164.92.251.245:8080/api/v1/products/)
  • requesting products with pagination functionality (limit, skip)
  • requesting products continuously, simulate endless loading (based on bidirectional-stream)

What does the server do:

  • going to the url, download and save the csv-file, extract the products from it, save to your database
  • giving products with pagination functionality (limit, skip)
  • giving away products in stream

Services are raised in docker-compose, the client starts and executes requests with output to the console, and then exits.
The server continues to work

Separate services

Client
Server

Example external csv-product store source (if still works)
swagger-doc
products

If first resource isn't work - check this example:
swagger-doc

About

๐Ÿ” Product-storage service, work on gRPC. Client sends the URL to download products, and requests the result. The server transfer request to a third-party resource for .csv-file uploading and saves the products to own database.

Topics

Resources

License

Stars

Watchers

Forks