Changing Service Purposes & Showcasing our app like a Netflix clone

[dannyi96]

Need to define service purpose better Sales Portal : Just a basic first entry Service to display main page. Route request to other services when needed. Product Catalogue: Service to query and to list all products Catalogue Store: DB where all products are stored( mock from csv). Leads: Display set of tech leads. Oppurtunities: Display set of Oppurtunities Accounts: Get account details for all users ( ?? ) Payables: DB / process which computes payable info Receivables: DB / process which computes receivable info

Need to showcase as different type of app(the current app is overused). Maybe some kind of netflix clone: Sales Portal -> netflix-frontend Product Catalogue -> movies Catalogue Store -> movies-store Accounts -> recommendation payables -> recommendation-engine receivable -> trending ...

[ganesh-k13]

Shall I add sqlite3 or something more complex for DB?

[dannyi96]

You can. But best lets keep it simple - The "DB" services can just load some csv files( have it in memory ) and expose an endpoint for querying that csv file.

[ganesh-k13]

Sounds good. So I'll raise a few PRs for this issue. One by one we'll tackle the services.

[dannyi96]

Have created a basic skeleton for the Netflix app which we can build upon in dev branch.

We have to

• better define each service's functionality and make them generic (work based on parameters supplied)
• Use a proper Netflix dataset for everything
• try to see how many more services we can create in this app to have longer traces and not make the graph look bad/too cluttered

We could make those trending services, etc to refer to some Telemetry DB and add more endpoints. Any other suggestions ?

[ganesh-k13]

Please merge any changes to NetFlix app to master. I want to work on DB