You are viewing a single comment's thread.

view the rest of the comments →

neogag ago

  • What kind of product licensing? Please tell me you aren't paying for Microsoft SQL Server. Replace all those licensed products with open source equivalents.

  • Maybe silly suggestion, as I haven't seen your codebase: benchmark and optimize so you can use cheaper hardware to host this thing.

PuttItOut ago

The code has just recently gotten to a place where we can optimize it. It is on our list but we need staff, it's simply too much for me to continue doing alone. So, if funding does happen, this will be one of the first things done.

We have been working our data access code to be able to port to pg, but to answer your question, sql is not a significant cost for us right now. This will not always be the case.

go1dfish ago

sql is not a significant cost for us right now. This will not always be the case.

What is? bandwidth? CPU?

sakuramboo ago

Bandwidth is always the killer. Storage is always pretty cheap, especially on AWS.

neogag ago

The site is all text which compresses well with gzip, so I wonder if it really is bandwidth that's the issue. He mentioned licenses, I'm dying to find out what product licenses!

sakuramboo ago

Text doesn't get compressed when transmitted, though. And, with the added SSL layer, that's even more.

Bandwidth is always the cost killer of any site, unless you are a specialized company dealing in big data or data processing, etc. You pay for every bit that goes in and out of your network. So, that asshole who hits F5 for 2 hours because you called him a lame-ass, unless your site has a free caching service, you are paying for that.

Yes, licensing costs are also a huge factor, but not as bad as it was 15 years ago. However, I do agree that porting everything to Linux/PHP/Postgres would be a pretty big cost savings, too (though, not as much as one would think. Azure/AWS is still pretty cheap).

heebykikeburger ago

Could a restful/dumb backend with something like React on the client save a shitload of bandwidth?

neogag ago

I'm launching a service soon and that's what we're doing. There is no need for complex abstractions on the server side (MVC); Microsoft platforms encourage that, but it's a huge hindrance and reduces productivity.

If you go with REST, you can go stateless (JWT) and not maintain session on the server at all. This lets you scale horizontally very easily.

heebykikeburger ago

Nice very modern.