here is the 

Code base setup
Low level design
Migration of stock process
Use JPA Query as much as possible
Integrate validation
Audit the record
E2E testing
Logic app trigger
Performance testing

undertsand how to process the file in blob which partner will put with file formt variability.....so that final is most probably a json to be send to beam...
after we have this doc at high level.....we will present to engineering team to discuss low level things...whether this present strategic design holds good for servicing
all partners as we had issues once during prod rolllover for one of the partner

How files to comes to us once file basically will come to us then how exactly we will process OK so solution at a high level, OK.

 whatever that we are developing currently that should something be used for all the international partners.
 
 basically file we have to process and then we have to generate data for them. OK so file format will be different. OK, so different partner may send in a different format. OK, so we'll get the file.
Yadav, Jitendra 5 minutes 39 seconds
Then basically we have to transform that file in a common format and common format is basically expected Jason

So mostly file, but they'll drop in, you know BLOB. OK so basically this.

Jitendra's request for a high-level overview of how files will be processed, indicating that clarity on requirements is essential for effective project execution.


File Format Variability: Jitendra pointed out that different partners may send files in various formats, necessitating a common format (e.g., JSON) for processing. This highlights the technical complexity involved in standardizing data inputs.


Step 4: Standardize Data Formats
Determine Common Format: Agree on a standard file format (e.g., JSON) for all partners to use.
Create Guidelines: Develop guidelines for partners on how to format their data submissions.


undertsand how to process the file in blob which partner will put with file formt variability.....so that final is most probably a json to be send to beam...
after we have this doc at high level.....we will present to engineering team to discuss low level things...whether this present strategic design holds good for servicing
all partners as we had issues once during prod rolllover for one of the partner


Comments  Cato  1. Database configuration -> not going to change.  2. Partner wise reading file -> not going to change.  3. Logic app -> ReadFileTrigger PerPartner -> Call endpoint (Partner information, file data) - 3  4. Codebase setup, Pipeline (dev, stage) -  5  I  5. Req  6. StockController -> General Services -> Partnerwise Services ->Generate Object based on file type -  7. Selling PriceController -> General Services -> Partnerwise Services -> Generate  Object based on file type -  8. StoreController -> General Services -> Partnerwise Services -> Generate Object based on file type -  9. ObjectForStock (Input Partner wise), ObjectForSelling (Input Partner wise ), ObjectForSale(Input Partner wise), Common object, Output Object -  10. Validator (Partner wise), Common validator -  11. Audited (Partner wise), Common Audited Message (Coding perspective)  tions On Editor Suggestions Showing  100%
....rephrase it