8/31/2023 0 Comments Stack overflow sql![]() ![]() ![]() There was someone on Reddit commenting on the 37signals cloud exit who believed that normal datacenters have 99% availability! Actual figure for most well run commercial DCs: closer to five nines. HA: Some people have extremely distorted ideas of how reliable server-class hardware and datacenters can be. > Except yours doesn’t have high availability or horizontal autoscaling It's a bit more direct than Docker, and gives you the traditional stuff like OS managed security updates (for the libraries the OS provides). You can sandbox the server with an additional line of code, define cron jobs with a few others etc. You can run it on Mac/Windows too and it'll build a package for your server, upload it, install it, start it up etc to a list of servers defined in the config. You can use Docker but I've written a tool that does it without that, just using systemd and Debian packages. Oddly, the most painful part is uploading servers and making them properly start up, be backed up etc. ![]() DNS editing is easy, just use your registrars UI for it. Remote admin and access controls are already handled via SSH and ordinary UNIX permissions. Wget -O /tmp/netdata-kickstart.sh & sh /tmp/netdata-kickstart.sh Install Ubuntu then:Īpt-get install certbot unattended-upgrades systemd-journal-remote This is how you can satisfy those needs with stock Linux. > log storage, certificate expiry, access controls, patch management, health monitoring, and remote administration, etc for more advanced use cases use a paid service (new relic) or a free one (nagios)ĭon't get me wrong I use cloud on a daily basis for work, I'm just sad because most teams don't know how to use it effectively without jumping the gun. in terms of lb nginx has that built in. enable unattanded upgrades for security patches Yes it's more work upfront but after you do the setup the first time there's little to do.Ĭertificate management (on LB machine only): But don't forget to always keep an eye on your bills and think how can you reduce them by simplifying your architecture.īut if you're just building a corporate intranet for a few dozen users who log in once a week I'm pretty sure a simple VM (even if managed in AWS) would make much more sense.Īnd if you really want to roll your own there are plenty of options to make your life much easier compared to sending a rocket into outer-space. Is time to market critical? Will you have daily traffic fluctuation between 10 to 10k users? Will you lose a ton of money/customers for any service interruption? By all means use the latest version of managed kubernetes combined with whatever other cloud service tickles those itches. It all depends on what you need and what are your specific constraints. Of course there are trade offs in terms of convenience but there are also trade offs in terms of cost and performance and vendor lock-in. I'm not an "on-premise bare-metal server absolutist". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |