Our client has a requirement where the user has multiple addresses associated with himself/ herself. In addition to this the customer should be searchable using the postcode of the address. We are thinking of managing addresses as different objects and maintain relationship between user and address. This would be a one to many relationship mapping.
We are using PostgreSQL for our IDM backend and using explicit mapping. The customer base is more than 10M
– Is going with relationship between objects a good idea with such a large user base? If not what is the alternative?
– Do we need to tune our database schema for this? If yes what kind of tuning are we talking about?
– Have you seen this done in any CIAM project. How was the performance?