Regarding reliability: all the code is opensourced and if you want to use the service in production - you can run this on your own server.
I wanted to make an analog of http://embed.ly/code but lost interest in the middle.
I can code difficult logic and all the highload server stuff but when it comes to front end, billing, images etc.. I'm getting bored too quickly.
If someone wants to help me make a business out of this: mdxytop at gmail.com
It is running for more than 2 years now, never failed :)
Golang is pretty stable.
Also the server is behind Cloudflare which caches responses and protects from DDoS, this can be another reason for low RPS to the server.
I love the idea of just serving a production HTTP API from a single go file.
Golang produces native code with very good runtime with green threads which makes it very easy to do async programming and write efficient network code. But language won't save you from inefficient algorithms and dumb code of course.
> I love the idea of just serving a production HTTP API from a single go file.
You may have mistaken by single Go file in my service but it is actually a lot of code included spread across several libraries. In order to write this service I had to write my own open graph library, oembed library, html parsing library etc..