You're going to have outages in production. They're inevitable. The question is how to best minimize outages, both their frequency and duration.
Common wi...
I agree with the sentiment of your article and I’m looking forward to seeing your follow ups. I’m always trying to keep things as simple as the problem I solve allows for.
Not a bad take per-se, but a bit condescending. While I agree and like the KISS paradigm, remember that no solution works at a lower complexity level of the problem itself.
So, define your problem clearly, find the simplest possible solution. Don’t overcomplicate, I agree, but don’t be fooled by false hopes.
Is it really simpler? Yes. Will it scale if I need it to? Maybe not, but will I really need for it to scale?
I understand this take and the frustration it is born out of, however, extremes are rarely the right answer. If this were a series of posts, I would gladly read along and expect that the author would learn some valuable lessons from this approach.
Are certain things often needlessly complex? Sure. Does that come at a cost? Sure.
However as a business (or deployment) grows, it becomes subject to more requirements, regulations, risks, etc. that often demand the complexities that the industry and author have witnessed.
All business decisions are made through a lens. What is important today? Based on what I know today, what does the future hold? What constraints do I have? The key is a logical, but balanced decision.
Hi friend, this was just meant to be an introduction, as I get started blogging and sharing back some knowledge and lessons I learned along the way. I’ve never written a blog before (or much of anything!), and I’m sorry you didn’t find value in this.
I wasn’t intending to boast, but I can see how it came across. I just meant to say, “companies are trying to tell you that you need ‘XYZ’ to scale,” and at least at the size of business I ran, you didn’t need any fancy tech at all – we could have made do with a dead-simple setup: a single server running Go and SQLite. It’s something I wish I had known when I started.
I’ll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.
I can offer some constructive tips to you as well: dont speak for all of us.
I liked the article. I didn’t interpret it as “everyone must do what I say”. It was simply a viewpoint from a person on the internet. That is what a blog is.
The complexity of tech stacks have increased enormously in the last 10 years, and it’s only sane to see what tradeoffs we are making to be able to scale easily. Perhaps it’s not worth the trouble for 90% of us. If we follow best practice from cloud providers without thinking for ourselves, we will not learn to think for ourselves either.
So let’s do that. Let’s think, wrote blogs, discuss, and allow for discussions. Don’t shut people down.
Is it too late for, “I use nix btw”? I use it at home and for development.
I planned to focus this blog series on ol’ faithful (Debian), but I could definitely see writing articles on how to use Nix and OpenBSD if people find it helpful.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I agree with the sentiment of your article and I’m looking forward to seeing your follow ups. I’m always trying to keep things as simple as the problem I solve allows for.
Not a bad take per-se, but a bit condescending. While I agree and like the KISS paradigm, remember that no solution works at a lower complexity level of the problem itself.
So, define your problem clearly, find the simplest possible solution. Don’t overcomplicate, I agree, but don’t be fooled by false hopes.
Is it really simpler? Yes. Will it scale if I need it to? Maybe not, but will I really need for it to scale?
And so on.
I understand this take and the frustration it is born out of, however, extremes are rarely the right answer. If this were a series of posts, I would gladly read along and expect that the author would learn some valuable lessons from this approach.
Are certain things often needlessly complex? Sure. Does that come at a cost? Sure.
However as a business (or deployment) grows, it becomes subject to more requirements, regulations, risks, etc. that often demand the complexities that the industry and author have witnessed.
All business decisions are made through a lens. What is important today? Based on what I know today, what does the future hold? What constraints do I have? The key is a logical, but balanced decision.
removed by mod
Hi friend, this was just meant to be an introduction, as I get started blogging and sharing back some knowledge and lessons I learned along the way. I’ve never written a blog before (or much of anything!), and I’m sorry you didn’t find value in this.
I wasn’t intending to boast, but I can see how it came across. I just meant to say, “companies are trying to tell you that you need ‘XYZ’ to scale,” and at least at the size of business I ran, you didn’t need any fancy tech at all – we could have made do with a dead-simple setup: a single server running Go and SQLite. It’s something I wish I had known when I started.
I’ll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.
removed by mod
I can offer some constructive tips to you as well: dont speak for all of us.
I liked the article. I didn’t interpret it as “everyone must do what I say”. It was simply a viewpoint from a person on the internet. That is what a blog is.
The complexity of tech stacks have increased enormously in the last 10 years, and it’s only sane to see what tradeoffs we are making to be able to scale easily. Perhaps it’s not worth the trouble for 90% of us. If we follow best practice from cloud providers without thinking for ourselves, we will not learn to think for ourselves either.
So let’s do that. Let’s think, wrote blogs, discuss, and allow for discussions. Don’t shut people down.
removed by mod
You just criticized the OP for the exact same thing.
removed by mod
It was clearly a setup for more content to come…
I think fans of Nix and NixOS would agree.
That’s interesting. I never got started with nix because I thought it’d be too complicated. So looking it up again…
Is it too late for, “I use nix btw”? I use it at home and for development.
I planned to focus this blog series on ol’ faithful (Debian), but I could definitely see writing articles on how to use Nix and OpenBSD if people find it helpful.
removed by mod
Well, I guess nixos itself isn’t too overcomplicated, but fun begins when you start layering abstractions over abstractions 😁