I have been asked to come up with a design for streaming data to the cloud. I have a closed system on a local server. I need to stream recently registered customers or updated customer records on the local DB to a cloud-based CRM and make data available to serve the firm's website. I came up with following design flow:

• executable to access the database on the local server and post records to the cloud server. This runs every hour. (1)
• A cloud server on which an api is hosted (2). A client (exe) calls the CRM Api to post records (3)
• Website gets(4) via api call.
• Data for website viewing is different from the data posted to CRM

It is ok to have 1 hour delay before customer records appearing on the website/CRM. Any suggestions for improving the design and making it robust with regards to connectivity etc...

I have been asked to come up with a design for streaming data to the cloud. I have a closed system on a local server. I need to stream recently registered customers or updated customer records on the local DB to a cloud-based CRM and make data available to serve the firm's website. I came up with following design flow:

• executable to access the database on the local server and post records to the cloud server. This runs every hour. (1)
• A cloud server on which an api is hosted (2). A client (exe) calls the CRM Api to post records (3)
• Website gets(4) via api call.
• Data for website viewing is different from the data posted to CRM

Any suggestions or feedback/criticisms on the design with regards to connectivity etc.. is there a better way to streaming data from closed systems.

I have been asked to come up with a design for streaming data to the cloud. I have a closed system on a local server, I need to stream recently registered customers or updated customer records on the local DB to a cloud-based CRM and make data available to serve the firm's website. I came up with following design flow:

• exe to access the database on the local server and post records to the cloud server. This runs every hour. (1)
• A cloud server on which an api is hosted (2). A client (exe) calls the CRM Api to post records (3)
• Website gets(4) via api call.
• Data for website viewing is different from the data posted to CRM

It is ok to have 1 hour delay before customer records appearing on the website/CRM. Any suggestions for improving the design and making it robust with regards to connectivity etc...

I have been asked to come up with a design for streaming data to the cloud. I have a closed system on a local server. I need to stream recently registered customers or updated customer records on the local DB to a cloud-based CRM and make data available to serve the firm's website. I came up with following design flow:

• executable to access the database on the local server and post records to the cloud server. This runs every hour. (1)
• A cloud server on which an api is hosted (2). A client (exe) calls the CRM Api to post records (3)
• Website gets(4) via api call.
• Data for website viewing is different from the data posted to CRM

It is ok to have 1 hour delay before customer records appearing on the website/CRM. Any suggestions for improving the design and making it robust with regards to connectivity etc...