496 karma · joined July 14, 2014
Im in the process of making my own static site, and im storing as much of configuration and content as possible in json.
Generally, our public APIs follow a standard set of best practices:
- All APIs follow REST principles.
- JSON is the standard payload. Some APIs may include additional formats such as XML and in such cases media type headers are used to specify your preference.
- Due to the sensitive nature of most data that is exchanged with American Express, you will commonly find HTTP POST methods used where you may expect to find either GET or DELETE methods used. The primary purpose is to prevent sensitive search criteria from being used in the Query string, moving it instead to the Body.
----------------
So they claim to be RESTful yet not support GET or DELETE calls. Do they even realize what they are saying?
[1] https://github.com/nerevu/riko
Edit: HN submission
Good idea, what are your workflows?
Next up I think would be supporting custom sources/sinks such as Twitter, HDFS, RDMS, etc. What exactly would be involved in "porting" riko to concord and what would the advantages be for doing so?
That's pretty impressive! So something like react/elm hot reloading?
Just gave it a look. Took a while to find some examples with code, but once I did it made a bit more sense.
> Beam is runner-independent and you can take the same code and run it at scale on a cluster, wether it's spark, flink, or google cloud.
I thought that was pretty cool.
> As for riko more specifically, Beam will have soon a python sdk, but I'm unsure if there will be a python standalone runner. Maybe this is something to look into...
A python standalone runner would be very useful. Otherwise I'm hesitant to go much further since my goal is to have a pure python solution for working with streaming data. Most libraries require installing java and that is what I'd like to avoid.