[xytop]

For absolutely 0-cost you can use http://proc.link which will return oembed info for ANY url.

General example: http://api.proc.link/oembed?url=http%3A%2F%2Fpage.rest

Youtube: http://api.proc.link/oembed?url=https%3A%2F%2Fwww.youtube.co...

Facebook: http://api.proc.link/oembed?url=https%3A%2F%2Fwww.facebook.c...

[afshinmeh]

Very neat. But the question is, how they pay the cost of the server? I mean, do you think a web service without any API keys, subscriptions, etc. is reliable?

[xytop]

It's my own server and I'm the developer of the service ;) I pay $3/mo for hosting and $10/y for domain so it doesnt cost me much.

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.

[afshinmeh]

Cool and just being curious, why did you run the server yourself? Just to have a playground or a demo for the project?

[xytop]

Idea was to make a profitable service out of this. But I'm bad interpreneur :)

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

[have_faith]

What levels of traffic does your server see on a normal day? has it ever gone down from a spike?

[xytop]

Usual traffic is 0-1 req/sec. Even now it is about 2-3 req/sec.

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.

[isgolanggood]

I'm shocked to hear more and more people running an HTTP api from a $5 DO instance. It's enticing enough for me to learn, but I want to know, what makes golang so scalable?

I love the idea of just serving a production HTTP API from a single go file.

[xytop]

It's not DO. It's scaleway C1 arm server, even cheaper.

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..