Ozon wants to create a rubric for buying cars. How to design this under the hood considering the existing monolith and non-relational database?

To add a car purchase section to an existing monolith with a non-relational database, several aspects need to be considered:

1. Analysis of the current architecture:

   • Understand how the monolith is structured, what services and modules it contains.
   • Determine how the current information is stored and processed.

2. Data modeling:

   • Create a collection for cars in the non-relational database (e.g., MongoDB) with necessary fields (brand, model, price, specifications).
   • Think through indexes for quick search and filtering.

3. Integration with the monolith:

   • Add a new module or service within the monolith responsible for the car section.
   • Use existing authentication and authorization mechanisms.

4. API and interface:

   • Extend the monolith's API to work with the new section (CRUD operations).
   • Provide a user-friendly interface.

5. Performance and scalability:

   • If necessary, allocate part of the functionality to a separate service (microservice) if the load increases.

6. Testing and deployment:

   • Conduct integration testing.
   • Ensure a smooth release without disrupting existing functions.

Thus, the design involves expanding data in the non-relational database, adding corresponding functionality to the monolith considering architectural constraints, and ensuring user-friendly interaction.