Based on how I understand the service, I’d posit you could run such a thing on Heroku for free forever, maybe spending a few dollars (7 usd) a month eventually if you needed some scale.
Yeah. It's one rate a day x 33 currencies x 19 years, so a total of 250,000 numbers. You could compress the whole thing (500 KB?) and serve it to a million customers a month for free.
Wouldn’t it be more reliable to ask the ECB to support JSON alongside xml? Or require them to provide JSON by law? Shims are fine, but technical debt. Fix the problem at the source.
This doesn't make any sense to me. Whether you have to use xmlParse() or jsonParse() is completely inconsequential. It's like writing laws that require languages to have a built-in XML parser. Or a fetchAndParseXml() function.
If these kinds of laws infected tech, we'd still be maintaining government mandated SOAP/WSDL services and other overly complicated tech that someone somewhere thought was the global maximum.
You'd enshrine in law a particular technical format? What is the cost of making such a law vs the cost of a different - but still very much usable - format?
I would, with lifecycle and sunsetting requirements. Laws are requirements docs with more ceremony and stakeholder participation, but also with much more authority.
That all seems well-intentioned and plausible in terms of how things should have been originally. However,
1) I can't help but think of all the problems that apply in general to specifying requirements (too vague, too constraining, too expensive to hammer out to sufficient precision).
2) That's different from changing it retroactively. Would you change it again when JSON goes out of fashion? Or mandate HTTPS? I've not read the OP in detail, but the impression I have is that the existing service is very much functional. Even ignoring the cost of changing the law, do we really want our public institutions to be in breach of law whenever fashions change? I'd rather let them set their own priorities to a large extent - for example, specify a very general, minimal set of requirements and do better when they have capacity to do so. I'm fine with people building on top of that where convenient. It seems like a good thing, in fact.
Off-topic, and regularly repeated, but people up/downvoting based on (dis)agreement is the second biggest annoyance of web forums (right after Android keyboard autocompletion).
That ECB link gives the latest rates. They also have one that give the last 90 days of rates [1].
There is a more general system for accessing ECB data that includes a vast amount beyond exchange rates, described here [2]. I think that lets you get anything they have in their statistical data warehouse. (If you don't need to get it programmatically, they have a web GUI [3]).
The general system is also vastly more complex to use. I was quite happy when I found that 90 day link and did not have to deal with figuring out how to get what I wanted out of the general system.
- default api response is json format, this format is easy to parse then xml (eg directly usage in js/nodejs app..)
- server cost is not too hight , api response is only static json data (data are sync. on midnight), so price is only for bandwige
- i plan added crypto and comodities (like gold,silver etc)
Thank you for posting this! I had no idea this existed.
It looks like all the rates are published with EUR as a base currency, so if you wanted to get the USD <> KRW exchange rate, you would have to use EUR at an intermediate. This is probably good enough for most applications.
https://www.bankofcanada.ca/valet/docs