pREST : GOlang based RESTful API ( PostgreSQL database ) : https://github.com/nuveo/prest http://postgres.rest/
"Problem: There is the PostgREST written in haskell, keep a haskell software in production is not easy job, with this need that was born the pREST."
Dec 15, 2016: "Today the postgrest is not distributed a binary, need to install Haskell to compile. pREST in its 1.0 version will be binary distributed (cross compiling, run in Windows by example), so you don't need to have anything installed on the server to run. How old is Haskell and how many developers exist? Go has less years and more developers, if you need to fix a problem in postgrest turn where?"
"The reason the pREST was born was because of a lack of developer, I am using pREST in my company, I know haskell and my developers nothing, if you have any problem (in production) just sits in my hand (hand want that)."
Honestly, the authors seem to have no clue what they're talking about and were looking for a good excuse to build something cool :). Which is fine!
> "Problem: There is the PostgREST written in Haskell, not in Go"
Moreover, if you want to use something like PostgREST but need to extend it, and don't know Haskell, this is a completely legitimate problem. While I'm all for competing implementations, the pREST author's claim for why it's needed is inaccurate.
[0] By "like Haskell", I really mean "unreadable/unwritable by the team supporting it". This could apply equally to Ruby, Java, bash, SQL, JavaScript, and Python depending on the makeup of the team supporting it.
q: "What issues did you have with Haskell in production?"
a: "PostgREST doesn't provide binaries and building it is hard"
q: "Actually PostgREST binaries are provided for multiple platforms." [1]
a: "The real reason is we don't have Haskell developers here." Case closed.
From personal experience PostgREST is high quality work; a set it and forget it service that doesn't need babysitting. Bugs are typically about missing capabilities, as opposed to failures. "Low defect" Haskell that does what it says on the tin.
[1] I don't know exactly when binaries first appeared but they were available as of April 2016, about seven months before the first prest commit.