So, I'm working on a web service to access our weather forecast data (10,000 locations, 40 parameters each, hourly values over the next 14 days = about 130 million values).
So, I read all about RESTful services and its ideology.
So, I understand that the URL is addressed to ressource.
But what is a Rhesus source in my case?
A common use case is that you want to receive data on several parameters at a time in one or more places. Thus, it is clear that every value of its own URL is nonpritical and will result in hundreds of requests. I have the feeling that my specific problem does not fit into the RESTful template.
Update: . To clarify: There are two patterns for using a service. 1. Raw materials; rows and rows of data for multiple locations and parameters.
- Interpreted data raw data calculated on symbols (for example, the Sun and clouds) and other parameters.
There is more than one “forecast”. Different customers have different data needs.
The reason I think this doesn't fit into the REST pattern is because, although I do have a “predictable” resource, I still have to supply a lot of request parameters. So a simple GET request to ressource does not work, I end up getting POSTing data.
source
share