Hi, nice idea! It went down though so I was thinking maybe you could build it strong but on the cheap too without needing a database and very little coding.

It starts with this premise: https://aws.amazon.com/articles/1434/

There is an approach I've used for years and my site never goes down with high traffic and I didn't use load balancers or anything fancy. Its very cheap to run and maintain.

1) Use Amazon S3 and Cloud Front for all your web pages, including your web app as well along with storing anything such as file uploads, etc.

2) Have a simple cheap $5 Digital Ocean Droplet (Node or Go) used only as an API.

3) JavaScript is hosted on your website front end that upon save for content then hits your API server just once to get a Just-In-Time signing request that authorizes the web browser to make an upload directly to S3 temporarily and signed to a specific namespace/bucket. This type of traffic happens very less than say viewing a web page along with it taking up very little processing and bandwidth so you really don't need to scale this.

4) The web browser's javascript literally creates the entire html page and uploads it directly to S3.

You can easily do image uploads as well or video too using this method and use the just-in-time signing method for those too.

Yes it is not secure if there is no signup etc but you can do crypto.generateRandom to put people in specific namespace path then show their URL after, controlling limited permissions and the location of where things are saved from your cheap API server.

Here's my little repo for signing to demonstrate this -> https://github.com/sebringj/siggy

Just a thought.

You may also use AWS Lambda and AWS API Gateway.

Sure you could. The funny thing is, I've had this product on the market using this very concept of JIT signing, using the browser (and apps) to do all the work, didn't really put any effort into, only used for my clients as a CMS-as-a-service or CMSSAAS WTF? called kitgui.com, been on some department store brands using it for ecommece sites that i've put as a consequence of needing this on multiple backend platforms. Any hoo, never goes down, never had to do jack shit scaling or worry about it but I've completely neglected it so it looks like 2010 crap themes and diy web standards. Anybody want to partner up on it and make a bad-ass json cms that spreads to all devices? I'll gladly divvy % on current revenue.

You could maybe convince me that this is good if you cared enough about it to host an instance yourself...

Alas, only doing this for karma and a false sense of belonging, beyond that, I like money.

Hello creator. You can handle the traffic and db insert on a cheap digital ocean plan.[1]

My server purred with hn traffic.

[1]: https://idiallo.com/blog/handling-1-million-web-request

For the record, firefoxd's static assets were offloaded to another server for an additional $10/month. $15/month is still not bad, but I feel like this comment is a bit misleading.

You reminded me of Nepter on Adventure Time.

How many requests-per-second are you getting right now?

What's the CPU utilization like with this level of usage?

What's the back-end stack?

What's the normal latency like?

I'm just wondering why it would go down due to heavy traffic, when all it serves is basic text?

> Write something, hit publish, and it's live.

Live for how long though?

Too many publishing platforms sunrise and sunset. To use one that's not self-hosted, I really think one either needs to (1) charge money, and/or (2) offer guarantees like Posthaven or Svbtle, if you want users to publish good content on your platform.

Write something, hit publish, enter resulting URL into archive.org?

I'd worry that's an abuse of archive.org except apparently their policy is basically "the crap is important too".

Even archive.org is dependent on donations [1].

[1]: https://archive.org/donate/

Well, yes. But it has already proven staying power that puts it in rather a different class to "somebody's neat side project" in terms of expectation of survival.

With the coverage you're getting, I'd expect traffic to go up indeed! Great work :)

http://www.theverge.com/2017/2/23/14712352/txt-fyi-minimalis...

Hey! The about says 'no databases', but how do you store the text then?

Storing in S3 should just work. Isn't it?

I'd imagine for the time being you could use DO's resizing features to vertically scale your droplet to handle the load. Then at a later point, horizontally scale.

Cool idea. You need favicon, so it looks nicer when bookmarked or saved in dashboard sites, like zeerka.com

I'm really curious what ended up being the thing that took you down.

The bottom line is I don't know beyond memory. I'm utterly amateur and have enlisted the help of another Hacker News reader!

"Utterly amateur" => runs boingboing.net.

No need for modesty.

Rob doesn't technically "run" boingboing -- they Have Ken Snider sysadmin'ing it ....

Yes, I'm just editorial (and until recently design). Ken is our sysadmin and, as it happens, got txt.fyi back on its feet today when HN blew it down! He's brilliant!

So... what was wrong? :D

Hey, consider Google Cloud as a solution, super low cost and scales automagically, load balances etc.