I'm not sure that the TMF SID model is intended for actual implementation as-is. It's a very comprehensive conceptual model shedding light on the information needs in the service provider domain. But the model is very heavy on deep class hierarchies, has strict (some would say austere) normalization, and is economical with attributes.
The Open API resource model, which is spiritually and methodically derived from the SID, is probably an easier basis for a persistence model, given that it is simpler as well as field-tested in real implementation.
But this is just my opinion
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Apr 07, 2023 03:18
From: Ravi Maddi
Subject: Do you know any experience of building system based on SID model on AWS DynamoDB ?
Hi Sergi,
A document db will be a better choice as Product, customer can hierarchies where embeded document structures work well. Key value pair may work for elements like usage or invoice detail.
The update strategy and version management in document db depend on the model, embeded vs referenced.For key value pair the attribute level updates seem simple but creating the full picture taking the latest instance will require more effort.
Thanks,
Ravi
------------------------------
Ravi Maddi
Tata Consultancy Services
------------------------------