9 ms·
Majority of web apps could just run on a single server
- LtWorf 3y agoHard to judge when I have no idea of how many servers are used by anything I access.
- nadermx 3y agoA $5 VPS, with almost any app, can handle the front page of hacker news. If I remember correctly I'd even venture to say hacker news runs on a one or two core box. It should be the standard
- abound 3y agoHacker News might not be the best example, as it seems to get overloaded once every week or two, usually when a contentious/high volume topic comes up.
- polishdude20 3y agoAnd despite that, hackernews is as popular as ever. I think the moral of this story is that having some downtime isn't a big deal.
- Macha 3y agoMy impression is that your standard wordpress + Apache + mod_php + mysql on same server install cannot, without plugins that improve wordpress' caching behaviour, and that's a large portion of the sites that do fall over.
- erik_seaberg 3y agoThree machines get you availability that one machine can't.
- ethanwillis 3y agoThat is not strictly true and entirely depends upon the machines in question.
- erik_seaberg 3y agoTrue, I'm assuming commodity hardware. I've never had the privilege of working on really high end systems, but my impression is that you buy or lease a cluster in a box that is simulating one reliable computer.
- ocdtrekkie 3y ago"The more they overthink the plumbing, the easier it is to stop up the drain." - Scotty, and good IT people everywhere. When you add all of the necessary layers of abstraction to get three computers to act as one computer, you added dozens of new points of failure. In the conventional case, yeah, you can now shut one down and people aren't impacted. But there's now a bunch of new ways it can break and take the system down and it is much harder to figure out why.
- wmf 3y agoThe question is whether you need active-active or if failover will be enough.
- eddd-ddde 3y agoWe use k8s at $JOB for literally no reason other than some engineer decided he wanted to learn k8s. It's the worst, I don't even get to see my server logs because "that would mean giving you access to the entire thing". I'm not a k8s person but surely that has to be missing something. We could literally make do with a cloudflare 5$ plan and have left to work with. With better integration, and better DX.
- tayo42 3y agoThat's not a k8s thing. It's an idealistic DevOps thing. You'd probably deal with that in alot of places.
- amtamt 3y agoThat for sure is not "idealistic devops", but someone missing fixing RBAC to let devs have access to logs of their workload.
- tayo42 3y agoMaybe without details or knowing exactly what he means. But I've worked with people that decided you don't get to see any logs on a server except for a select few through some web ui or a log aggregator.
- eddd-ddde 3y agoI know what you are talking about, unfortunately it's way worse than that. The same guy that runs the k8s is the guy that "reviews" my PRs. It's also the same guy that can't get eslint into our PR process, and the same guy that merges code from other people that just out right brick the server because it had some bad syntax. I _wish_ my problems were caused from too strict standards and procedures. But really is just a lack of understanding and cooperation.
- amtamt 3y agoThere are production systems handling PII (finance, healthcare etc), where logs are treated as radioactive and only people with trust, training and protective gears should be touching them. This is the case where these are legal/ compliance requirements. Non-prod of those systems can have wide open access to logs, unless someone decides to import prod data for "testing" in non-prod. While I agree access to logs may seem too restrictive, there are some very solid reasons for that... and then we have some cargo-cult and some lack of time/ understanding which causes too restrictive log access where it might not be required.
- zer0tonin 3y agoYeah, a 4$/month VPS can handle thousands of queries per second: https://alicegg.tech/2023/02/06/4dollar-vps https://alicegg.tech/2023/02/06/4dollar-vps
- deleted 3y ago[deleted]
- lewisjoe 3y agoI can confirm. I've had quite a few projects that made it to the front page of HN and handled the traffic like cake. All of them ran on 5$ digital ocean droplets. I accept some projects are more resource expensive than others, but majority of the time you can get away with a bit of asynchronous responses + scheduler/queue to spread the load horizontally over time. Unpopular opinion: I blame the new age devops culture that made cloud app deployments unnecessarily complicated with k8s and cool new tech (that'd get them high profile jobs.) I've never come across a devops person who'd say "Hey, that sofware is too simple to prematurely scale for sudden spikes of irrational amounts of traffic, so why not just deploy it on a cheap vps?"
- everforward 3y ago> I've never come across a devops person who'd say "Hey, that sofware is too simple to prematurely scale for sudden spikes of irrational amounts of traffic, so why not just deploy it on a cheap vps?" I work on the Ops side partially, and our platforms are defined by the highest level of complexity we need to support. That is to say that your basic web app can run on k8s, but that auto-scaling, messaged-based behemoth that 85% of the business flows through will not. So I can either support k8s, or I can support k8s _and_ old-school rsync deployments to VPS' The complexity of running a basic web app on k8s is entirely too high, but the cost of keeping an entirely separate deployment/monitoring/oncall/permissions stack for VPS' is worse. Better hope your monitoring vendor has an agent that can run in a VPS' on the OS you want, or you're back to running Nagios yourself. If at least 1 group is going to write an app that runs on k8s, you might as well run most of the company on k8s. Otherwise you're either going to manage 2 separate stacks, and/or try to write an abstraction layer that will probably itself resemble k8s.
- allarm 3y ago> why not just deploy it on a cheap vps? I’m that kind of a person and the usual response I get is - hey, that’s too complex!
- littlestymaar 3y ago> I've never come across a devops person who'd say "Hey, that sofware is too simple to prematurely scale for sudden spikes of irrational amounts of traffic, so why not just deploy it on a cheap vps?" It Is Difficult to Get a Man to Understand Something When His Salary Depends Upon His Not Understanding It
- deleted 3y ago[deleted]
- Animats 3y agoYes. You don't even need containers. Write your program as one Go executable and drive it from fcgi. Go is fast enough that you can get a lot of work done on a minimal server. Fgci provides "orchestration" of multiple processes, plus crash and restart handling. Also, there's much less attack surface. If your minimal Go program can only respond to specific requests, there's not the problem of an attacker targeting some unused feature of the site. Go has subscript checking, so you don't have buffer overflow vulnerabilities.
- moondev 3y agoYou don't even need to write your program in go or configure and deploy with fcgi. Write it in whatever you want and stick it in a container.
- throwaway63467 3y agoGo can even serve traffic directly without a frontend server, ACME support for TLS is also great.
- master_crab 3y agoCan the majority of webapps run on a single machine? Probably. Do most of your customers expect close to 100% uptime? Yes. Does one machine provide the uptime required by your customers? Most definitely not.
- userbinator 3y agoMake it two machines then.
- master_crab 3y agoYa. 1<n<6 has worked 99% of the time for me.
- Jgrubb 3y agoThe correct answer to question 3 is "it depends".
- sjducb 3y agoMaster slave failover will give you less than a second of downtime.
- hparadiz 3y agoPretty much any provisioned vm can be split down the middle. Got 4 cpus and 4gb of ram? Congrats you have two vms with 2 cpus and 2gb of ram. Throw them into a 50/50 load balancer and never have any downtime.
- toast0 3y agoTwo vms on the same machine doesn't help when the machine fails. Also, I sure hope your loadbalancers don't suck. I've worked with some that had worse uptime than my servers, and worse capacity too. Went back to putting the two host addresses in DNS, which is mostly fine, but means a lot of waiting when you want to take a host out of rotation for disruptive maintenance.
- toenail 3y agoIf you don't care about downtime or reliability, sure.
- Nextgrid 3y agoMost companies are too full of themselves to do an honest assessment of their uptime requirements though. Every company out there loudly claims they need 100% uptime, which grifters will be happy to sell them knowing nobody will actually put their solution to the test and if it does fail they'll have a myriad of moving parts to shift the blame to. If you look at the very few things that do actually need 100% uptime (real-time stock market, etc) you'll note the absence of most "cloud-native" and supposedly "best practice" bullshit. The reality there is much more boring, serious and rigorous - that's what you get when you actually need 100% uptime.
- throaway2342551 3y agoYou are aware bloomberg presents at CNCF?
- Nextgrid 3y agoBloomberg is a large company with many different products, people/teams and priorities. But as far as I know Bloomberg doesn't actually provide order execution which is what I was referring to when I said "stock market".
- viraptor 3y agoThere are very specific reasons why real time stock market doesn't run in the cloud and there's a lot they're doing that very much aligns with best practices. Your example doesn't really say what you seem to think it does.
- SkyPuncher 3y agoI’ve worked a few places that clearly stated: * we are not mission critical for our customers. Let’s not engineer for disaster scenarios when our customers really won’t care if we have a very very rare outage. * our customers primarily used our services during US business hours. If we needed risky maintenance, we’d just do it a bit early or a bit la tree in the day.
- sjducb 3y agoThe real reason for cloud micro service architecture is legacy code. Imagine you’ve inherited a 10 year old PHP monolith. The code is almost indecipherable and the business wants new features in a timely and predictable manner. The easiest way is to implement the new features in their own micro services. Sure it makes the complexity problem worse, but that’s a problem for someone else in five years time.
- bcaxis 3y agoYou could solve this other ways. Build a new better monolith and have a reverse proxy route between them and slowly update and move routes over. You will get through a rewrite slowly one bit at a time. If you keep the same database schema this should generally work pretty well. I migrated a terribly written web app this way, it worked pretty well.
- sjducb 3y agoThe application was written by a team of 20 over 10 years. There are over 3000 database tables. The job it does is big and complicated. It is used by teams all over the world. The problem is the inherent complexity of the business domain. Not poor quality code from devs 10 years ago.
- bcaxis 3y agoApparently I don't understand. If the code isn't poor, why throw it away for a new even more complex system? I don't know how code isn't poor, yet is indecipherable. Regardless, the method works even in a complex environment.
- feverzsj 3y agoIf your app doesn't server more requests than sqlite.org daily, you shouldn't pay more than it. > sqlite.org answers more than 500,000 HTTP requests per day (about 5 or 6 per second) delivering about 200GB of content per day (about 18 megabits/second) on a $40/month Linode. The load average on this machine normally stays around 0.5. [0]: https://sqlite.org/althttpd/doc/trunk/althttpd.md https://sqlite.org/althttpd/doc/trunk/althttpd.md
- charrondev 3y agoI mean it really depends on what your doing. If you’re just serving static content then of course you can get away with one small box. If you have user content that’s being constantly updated and inserted you need a lot more. You need databases, caches, and in our case elastic search (with ~10 billion documents). The data needs to be indexed 16 ways to Sunday to make sure that a user hitting the page with this filter or that sort selects just the right records. If you care about reliability you should have read replicas of your DBs as well. Where are your logs going? I’d expect servers for that as well. Now alternative to a bunch of this you could just use SaaS products but that costs an arm and a leg.
- feverzsj 3y ago> dynamic pages on the SQLite website typically do about 200 SQL statements each. [0]: https://www.sqlite.org/np1queryprob.html https://www.sqlite.org/np1queryprob.html
- johannes1234321 3y agoHow many of the request on sqlite.org go to the "dynamic pages"? I would assume by far most are on the static docs. The forum and other "dynamic" content is quite hidden.
- SQLite 3y agoAbout 10% overall (9.96% to be precise), according to server logs over the previous 10 days. Robots hit dynamic content at about twice the rate as humans: 14.12% versus 7.8%. About 34% of traffic is from robots, from what I can tell (though to be fair, many robots these days work hard to disguise themselves has human, so the actual percentage of robot traffic is likely much higher.)
- evrimoztamur 3y agoIn fact, a single five euro server can run: My personal website, Two multiplayer game servers for the games I built, frp for tunnelling; and I'm planning on squeezing more in until it gives up. All reverse-proxied by nginx under subdomains of my personal domain address, absolutely seamless. Similarly, other applications I built so far all also run under five euro VMs. There's no denying you might need more because you have serious peaks in traffic that you cannot handle with only one server, but do the accounting. It's a worthwhile decision to think through.
- makerdiety 3y ago> Similarly, other applications I built so far all also run under five euro VMs. There's no denying you might need more because you have serious peaks in traffic that you cannot handle with only one server, but do the accounting. A simple proportional-integral-derivative controller equipped onto your server resource can help you see if future traffic spikes are occurring. The question is, what kind of person is able to have that kind of perception ability and is willing to integrate that into his daily life? Not the average software developer, we can definitely say with great confidence.
- evrimoztamur 3y agoI'm partial to forecasting volatility via GARCH models as well!
- polishdude20 3y agoWait what would a PID controller do? What would it be controlling?
- makerdiety 3y agoYou're supposed to be repurposing the controller into a reporter. Since you don't need control, you can instead just use the PID portion of the PID controller. But you can also attach an actual automatic control for when the sensor reports a positive traffic influx prediction value. And I think stuff like Kubernetes includes this feature. Go figure.
- mcluck 3y agoI once worked a job where I easily spent 4 times as much time fighting with Terraform files than actually writing features. This company got less than 1,000 hits per day. I think about this a lot
- Nextgrid 3y agoI've had gigs where it felt like the company was spending more time fighting self-inflicted consequences of their "best practice" "cloud-native" architecture than developing actual revenue-generating features. So many problems they were dealing with would magically disappear if all the services were running on a single high-end physical machine (the scale didn't mandate anything bigger than that) with a standby one sitting in a different DC for redundancy purposes with incremental DB snapshots shipped to it every 15 mins. The cloud-native, "modern" infra became a liability and impediment to business but too many people would lose face to admit it.
- acabal 3y agoAt Standard Ebooks we serve a respectable number of page views and ebooks each month - and have been on the front page of HN three or four times - all of it done with a single 4GB VPS. And the only reason we upgraded to 4GB from 2GB is because we needed more RAM for the server to build the extremely large Decline and Fall of the Roman Empire ebook - if it weren't for that, our 2GB server would still have been just fine for all that traffic. I wrote a blog post about how we do it here: https://alexcabal.com/posts/standard-ebooks-and-classic-web-tech https://alexcabal.com/posts/standard-ebooks-and-classic-web-...
- eyegor 3y agoA lot of resources go to scaffolding for containers, runtimes, caching, etc. 4gb would make for a chugging experience if you run a Java spring boot backend for example. But an old school php + postgres stack would be fine, or modern dotnet, rust, etc. And honestly I'm not sure it matters since ram and compute is cheap for most small-medium sites (at worst maybe $30-50/mo vs $10-20/mo). VPS services are pretty cheap these days. Hetzner, digital ocean, genesis, etc. Or you spend a couple grand to build a dedicated machine in raid6 and only pay utilities.
- acabal 3y agoOf course. The entire point is that so much of that is just unnecessary for 90% of web projects. Most projects that are basically a front-end website backed by a local DB can get by on a 2GB VPS if they embrace classic web tech and don't get sucked in to whatever framework/cloud service/container craziness is hot this week. Once they start hitting millions of page views a month, we can talk about upgrading to 4GB :)
- LtWorf 3y agoRemember that rust doesn't catch all the memory leaks… So a long running rust process might degrade the performances in the machine, slowly.
- pdimitar 3y agoIf you can give examples on how does Rust leak memory, that would be informative. I had two services run uninterrupted for months in 2GB RAM containers. Memory increased steadily the first 5-10 minutes and then stayed there indefinitely long.
- jameshart 3y agoWhat kind of systems are people imagining when they picture 'the majority of web apps'? In this thread, I see people citing HN (a simple bulletin board system); or sites that will get linked from HN and have to handle load - so, presumably blogs, or CMS-backed marketing sites, maybe with a sign-up form or a single product ecommerce storefront? Sure, I can buy that you can run a pretty robust bulletin board or CMS on a single server. PhpBB and Wordpress with a Postgres backend will get you a long way. But if you think that's what all web apps are like, you're not thinking anywhere near big enough. "I've seen some stuff that's over engineered" is not evidence for "everything is over engineered".
- throaway2342551 3y agorunning etcd on a single node is wild
- aaronbrethorst 3y agoNo one's gonna promote you for proposing to build a monolithic app with the DB and queue on the same machine. Gotta have microservices built in Rust talking to micro-frontends built with the latest and greatest JS framework, all orchestrated by K8S running on a fleet of machines to seem hip!
- zeroCalories 3y agoGonna throw out an anti-cirlcenjerk take: We know. Absolutely no one has ever said that your super basic webapp that has the latency requirements of "make sure it works", an SLO of "it's fine most of the time", and a code base under 10k lines of code worked on by one guy, needs these super complicated systems. Even FAANG will run internal services and dashboards on a single binary, but when every second of downtime can be translated into lost money, then you begin to care.
- arnaudsm 3y agoI wouldn't say complexity and reliability are correlated, worse, it's an inverse correlation.
- zeroCalories 3y agoYes, programs that don't need to do anything can be very reliable.
- Yeroc 3y agoUnfortunately many of these super-complicated systems run at odds to having a reliable and fast, system even when every second of downtime can be translated into lost money.
- zeroCalories 3y agoRealistically, they are required. I don't care how you do it, but you need 1. Seamless fail overs 2. Easy horizontal scaling 3. Location based load balancing 4. A way to deploy and rollback all of these automatically. As a result, things are gonna get complicated no matter what you do. But as it turns out, using something like Kubernetes, Elixir, or AppEngine can make all of that very manageable.
- Yeroc 3y ago#3 is debatable for many, many businesses. The other three are (almost) trivial with a decent load balancer and blue/green deployments. This is something very achievable without an over-complicated architecture.
- barishnamazov 3y agoI have been running multiple web apps with decent traffic (each ~10K requests per day) at no cost at all. Oracle Free Tier [1] for backends with Cloudflare tunneling [2] and pages [3] for frontend integration. Works fully seamless. [1] https://www.oracle.com/cloud/free/ https://www.oracle.com/cloud/free/ (4 cores, 24 GB ram for free; switch to PAYG to avoid idleness shut down, but you still pay nothing) [2] https://www.cloudflare.com/products/tunnel/ https://www.cloudflare.com/products/tunnel/ (protects from attack and automatically connects your backend IP into your domain, e.g. https://domain.com/api https://domain.com/api will redirect to your backend) [3] https://pages.cloudflare.com/ https://pages.cloudflare.com/ (easy static page hosting, very fast deploys)
- Aachen 3y agoSomehow hearing of getting free hosting from Oracle makes me think of the advice to not stick your "thing" in crazy. It's probably fine, but I'd not touch it if it can be avoided, especially if I can just pay a small and fair fee at another provider (or, in my case, self host it)
- barishnamazov 3y agoIt was my reaction at first too. Luckily, I am not running anything super important or something requiring much privacy there (it's mostly computational services that don't store data). Since I am a student with no residence (and bad university network uptime), I can't self-host, but will do as soon as I move-in to my own place.
- EasyMark 3y agoI'm guess they probably use open source tech and such and can move it over to a new VPS in less than a day...
- OhMeadhbh 3y agoI agree w/ the sentiment, but the author doesn't seem to understand why people tend to like touching the customer at the edge. Since everyone is doing TLS these days, you have to do a TCP connect round-trip and a TLS round-trip before you can start yammering over a connection securely. So that's at least three round-trips. If you're one-way latency is 200ms, that's about a second of delay before things start happening. The benefit of the edge is you can establish a connection with an endpoint that's "nearby" with less latency for the TCP & TLS round-trips and then use a previously established connection (that does not require you to do the TCP & TLS roundtrips.) There's still latency, but the impact of the round-trips at connection time is reduced. Also, web-apps use horizontal scaling largely to reduce the impact of head of line blocking (where requests are queued up at the client waiting for the current request to complete.) Browsers will sometimes (often?) open multiple connections to the same endpoint to reduce HoL blocking impact. But, sometimes apps are inherently serial (you don't know what the next request is until you get the response back from the current request) so YMMV. Also... HTTP/2 and QUIC are cool, and I think most major browsers support either or both. Amazon is also sort of (in)famous for triple-redundancy. Their apps run in at least three different availability zones (think different data centers) to avoid the impact of one data-center going down. Sure, it doesn't happen very often, but Amazon REALLY doesn't want their site to be down at all. So sure... you COULD run the overwhelming majority of web apps on a single container in a small VM on a single machine somewhere, but it's more than just resource utilization. It's also responsiveness and resistance to single data-center failures. But don't confuse my comments with a callous disregard for the OP's concerns. Dude has a point. I think anyone who tries to deploy a web app to AWS (or Azure or GCP or ...) is barraged with messages about how you have to deploy things in multiple data-centers and you're not a REAL developer until you've crafted your own customized templating engine for spitting out TerraForm or CloudFormation scripts that automagically deploy to N+1 unique datacenters. There's probably a market out there for a simplified system that's "here's a simple {Node|Python|Ruby} app. Automagically distribute the backend to N different data-centers, maybe only one is up at a given time and the other N-1 are hot spares. And make the persistence tier indistinguishable from a local DB like Mongo or PostgreSQL (or some weird Prevayler-like thing.) Don't make me craft custom TF or CF to manage redundancy.)" Please note. I'm not talking about using SAM. To recap... I think the OP has a very valid point, but may not be familiar with all the current triple-redundancy dogma.
- deleted 3y ago[deleted]
- ByQuyzzy 3y agoMajority of tech companies could run on just a handful of nerds. But VC comes in, pretty soon you've got a bunch of lawyers telling you you need HR people, more lawyers, people to run ERGs. Soon you've got server farms all over the world to handle a couple dozen simultaneous users, thousands of employees, and you've made it! Then the board fires you.
- tombert 3y agoI built a site for my dad recently. There was no delusions that it was going to become the next YouTube or anything, but it does require a lot of number-crunchy stuff, so I could justify a slightly-beefier-than-the-minimum box on Hetzner. I had to resist every urge to do an elaborate Docker Swarm or Kubernetes setup, with replicated databases and async processing across message queues across different machines. I want to do that stuff, but realistically this site is going to get like 12 users a day at most, and doing that would have drastically increased the cost for really no perceivable benefit. I ended up just installing NixOS, and doing everything with Flakes, on a single machine with a Postgres database. It was cheap and easy, and it probably has saved me a lot of unnecessary headaches; most websites aren't going to be the next Google.
- dehrmann 3y ago> websites and apps get <10 rps and 50 on a busy day. This is very different from the majority of requests. The majority of requests are going to Google/Youtube/GCP, AWS, Azure, Meta, Netflix, and Clouldflare. I'm sure I'm forgetting someone, but you get the idea. Medium-sized companies are also past the single server point, and a lot of us will end up working at these companies. While the poster's statement is true, it's only relevant for hobby projects (unless your hobby is devops) and early-stage startups.
- rr808 3y agoMost over engineering is career driven development. You may laugh at the people who unnecessarily use loads of microservices, specialized tools and libraries, exotic cloud solutions etc. But the architects and senior developers who do this stuff now have great high paying jobs. If you choose the simple cheap solution the client might love you (realistically they wont know the difference) but you wont be able to get those high paying jobs. Ask me how I know.
- rqtwteye 3y agoTotally agree. Problem is that if you run your stuff on a single server you are at risk of being unhireable. Every interview I have been to, nobody asked about pragmatic,sp simple solutions that do the job, but they wanted to hear about microservices, k8s, Redis and other stuff. Based on the job postings, my company wouldn’t hire me because I don’t work with the stuff they are asking for. It seems a pragmatic solution for a dev to jump on these bandwagons. Right now it’s probably a good idea to push AI somehow into your systems. Doesn’t matter if it makes sense or not.
- pcblues 3y agoAmen. This is a full e-marketplace I mixed together as a demo. It runs on a USD$10/mth VPS. No other overheads, licence fees, etc. https://donate.pcblues.com/ https://donate.pcblues.com/ You don't have to worry about spiking because it's a "turn-based" business transaction site. So if you need two hours to shift to a larger server as the number of buyers and sellers increases, you have it.
- tky 3y agoNo lies. A shocking amount of architecture work is resume-driven development masquerading as “best practices” and often ends poorly. So many difficult to troubleshoot, needlessly complex, and less-reliable services exist for no practical reason. Lots of people need to remember they are not Google and should focus effort on what matters instead of “scale” they’ll never reach.
- arnaudsm 3y agoTech debt exists for the same political reasons than bullshit jobs. There are few incentives to simplify, and the bigger your budget the more internal political power you have. It's especially true at larger companies where it's ok to be inefficient thanks to your monopoly.
- johnklos 3y agoThere's a lesson to be learned from the trend to move everything to Kubernetes / Docker / one VM per function. Aside from the disadvantages of being reliant on others for timely updates and security fixes, people now believe that they need multiple gigabytes of memory to run what used to easily and comfortably fit on a single machine. This move is being sold through security arguments that attempt to convince people that there's no real security in Unix OSes, that if one service gets compromised, the whole server gets compromised. Hmmm... That seems very familiar... Where have we seen that before? Oh, right! Windows! Really, though, user-level security in Unix OSes has been refined and well understood for decades, yet now we're supposed to assume that people are too inexperienced to apply user-level best practices, and are therefore expected to just run everything in separate containers / VMs and not care about security because it's been delegated, roughly, to others? That's both kicking the can down the road and opens up nefarious possibilities like wide distribution of backdoored / compromised images and containers. "Don't learn for yourself - trust us, instead" is what I see. Really, though, I can, I have, and I do run more services on old Raspberry Pi and similar hardware than many people run on huge, 500 watt servers. It's both a waste of resources and a lost opportunity for people to participate more in their own systems' security, rather than delegating to the rest of the world where evil people constantly scheme to take things from us. I'll happily keep showing people how to properly set up software to coexist on a single Unix OS, and will continue to call out the "containerize everything" movement for trying to dumb things down.
- d--b 3y agoI am surprised that this is even a question, to be honest. Don’t people start with one server and scale up only if necessary?
- PeterZaitsev 3y agoDo not forget, for many, there is certain satsfaction and bragging rights in operating large complicated environment. Hundreds of Nodes, Thousands of Microservices is much more sexy than simple few nodes cluster It always amazed me how efficient software can be created than excessive capital is not available
- lightningspirit 3y agoDocker (and to an extend, Docker Swarm) is a good alternative where simplicity, lightweightness and stability are key points. Using it for almost 4 years in many projects with thousands of views each day, both on single or two VMs. No failures, no surprises, no pitfalls, automated CI via Git. No devops required.
- pacifika 3y agoThe majority of websites don’t have paid engineers
- p3rls 3y agoI have a small web development hobby company and I run it all of a $200 ovh server. We do like 10m pageviews, too. No problems once we figured out how to not crash during cronjob calculations.
- readthenotes1 3y agoAs far as I can tell, much of architectural choice is driven either by the need to be entertained by shiny new toys, or the need to pad the resume with shiny new acronyms.
- ijijijjij 3y agojust get a $10/yr VPS: https://lowendbox.com/ https://lowendbox.com/
- fatnoah 3y agoA long time ago, an F100 company acquired my messaging startup. We hosted client APIs and a web application for 2M monthly users sending 1B messages/month on a single AWS medium CPU server and a SQL Server DB. The rest of our infra was entirely for redundancy and monitoring to enable our 99.995% uptime. Post-acquisition, the AWS budget I was given to maintain our infra was almost 20x the actual cost, and based on infra that company used to host similar traffic.
- noop_joe 3y agoTo a large extent this is true. But a lot of the complexity is introduced as a way to deal with the operational effort of running software (HA, security, platform upgrades, backup/recovery, incident response, all that stuff). That doesn't mean it shouldn't be on a single server -- but a _lot_ of the motivation is preventing the dreaded 3am call.
- nrvn 3y ago“Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better.” — Edsger Dijkstra