4 ms·
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
by amerine 6y ago
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.
- toomuchtodo 6y agoWouldn’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.
- sambe 6y agoYou'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?
- toomuchtodo 6y agoI would, with lifecycle and sunsetting requirements. Laws are requirements docs with more ceremony and stakeholder participation, but also with much more authority.
- sambe 6y agoThat 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.
- toomuchtodo 6y agoI think your points are important, but it's likely we won't reach an agreement on this issue. Appreciate you raising the points though!
- polote 6y agoWhat is the issue with XML ?
- deleted 6y ago[deleted]
- XCSme 6y agoI don't see the problem with XML, especially today, when you can get a package/libray to parse any format the API might be in.
- LoSboccacc 6y agothere's some hip environment that handles xml quite badly compared to json and people with little cross experience think the problem is xml
- hombre_fatal 6y agoThis 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.
- rixed 6y agoOff-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).
- dmurray 6y agoYeah. 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.