Besides the usual APIs calls directly to CMX, we are thinking of exporting this to a database (SQL , Oracle etc..) instead as the requirements growth so we can offload the CMX instead of individual API calls to the CMX. Do you have any suggestion how this can be done?
We have a reply from CMX engineering regarding best practices on exporting CMX 10 data for offline use. In general, I think the philosophy is to provide APIs and not directly consume the underlying databases – postgres and Cassandra. As we port things to the cloud, we are changing the underlying databases even though the APIs may be roughly staying the same.
Another strategy which may be more useful is to use the northbound notifications and have them sent to a restful service that the customer provides. In this way, their own program collects the data and then they can store it however they see fit in their own databases. For scale, this works best.
Please sign in to leave a comment.