Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    Would depend on amount of data, data format (CSV, binary, JSON, XML...) and maybe a few other factors (also considering using another service if this one isn't reliable enough, though of course may not be an option for whatever reasons). There are various simple solutions for log data that could handle this maybe, one thing to look into could be the Elasticsearch ELK stack. Commented Jul 20, 2015 at 11:30
  • 1
    What resources are available to you? What (e.g. monetary) loss would your company endure if the data is fully lost? What is the volume of data and bandwidth? How serious/reliable is that web service to which you post? Is it under your control? Commented Jul 20, 2015 at 11:34
  • Did you consider doing the opposite. Have some kind of server on your machine, and have the web service pull that data periodically? Commented Jul 20, 2015 at 11:40
  • It's business critical that we don't lose any, or very minimal, data as it's for auditing for sensitive temperature controlled environments. We'll be using Json, and they will simply be sensor readings (not a large amount of data). We'll be using Web API, probably hosted on Azure, so the availability of the service should be good. Of course there are other factors such as localised network concerns. Everything will be under our control, apart from the infrastructure where the sensor software will be installed, this will be at client sites. Commented Jul 20, 2015 at 12:49
  • 1
    @DarrenYoung: you should edit your question instead of commenting it Commented Jul 21, 2015 at 5:15