If you are startup that can can’t afford a DBA, then why why why are you using Kubernetes?
Almost every infrastructure decision I endorse or regret
51–60 of 644 posts
Re: Almost every infrastructure decision I endorse or regret
#52Well it's a bit unfortunate this post was published in Feb 1st, it got really outdated really fast around the "choose flux for gitops" part.
Re: Almost every infrastructure decision I endorse or regret
#53So by and large I agree with the things in this article. It's interesting that the points I disagree with the author on are all SaaS products: > Moving off JIRA onto linear I don't get the hype. Linear is fine and all but I constantly find things I either can't or don't know how to do. How do I make different ticket types with different sets of fields? No clue. > Not using Terraform Cloud No Regrets I generally recom…
PagerDuty’s cheapest plan is $21 per user month
OpsGenie’s cheapest is $9 per user month but arbitrarily crippled, the plan anybody would want to use is $19 per user month
So instead of a factor of ten it’s ten percent cheaper. And i just kind of expect Atlassian to suck.
Datadog is ridiculously expensive and on several occasions I’ve run into problems where an obvious cause for an incident was hidden by bad behavior of datadog.
Re: Almost every infrastructure decision I endorse or regret
#54So by and large I agree with the things in this article. It's interesting that the points I disagree with the author on are all SaaS products: > Moving off JIRA onto linear I don't get the hype. Linear is fine and all but I constantly find things I either can't or don't know how to do. How do I make different ticket types with different sets of fields? No clue. > Not using Terraform Cloud No Regrets I generally recom…
> Cost is the most common complaint and it's almost always from people who don't have it configured correctly (which to be fair Datadog makes it far too easy to misconfigure things and blow up costs).
I loved Datadog 10 years ago when I joined a company that already used it where I never once had to think about pricing. It was at the top of my list when evaluating monitoring tools for my company last year, until I got to the costs. The pricing page itself made my head swim. I just couldn’t get behind subscribing to something with pricing that felt designed to be impossible to reason about, even if the software is best in class.
Re: Almost every infrastructure decision I endorse or regret
#55Earlier quoted context omitted.
The downside is then you have many, many DBs to fight with, to monitor, to tune, etc. This is rarely a problem when things are small, but as they grow, the bad schema decisions made by empowering DBA-less teams to run their own infra become glaringly obvious.
It's because I hate databases and programming separately. I would rather slow code then have to dig into some database procdure. Its just another level of separation thats too mentally hard to manage. Its like... my queries go into a VM and now I have to worry about how the VM is performing. I wish and maybe there is a programming language with first class database support. I mean really first class not just let me r…
> I mean really first class not just let me run queries but almost like embedded into the language
Not quite embedded into the OS, but Django is a damn good ORM. I say that as a DBRE, and someone obsessed with performance (inherent issues with interpreted languages aside).
Re: Almost every infrastructure decision I endorse or regret
#56Well it's a bit unfortunate this post was published in Feb 1st, it got really outdated really fast around the "choose flux for gitops" part.
Mind sharing bit more of the details?
> engineers at Weaveworks built the first version of Flux
> Weaveworks donated Flux and Flagger to the CNCF
https://fluxcd.io/blog/2022/11/flux-is-a-cncf-graduated-proj...
> Weaveworks will be closing its doors and shutting down commercial operations > Alexis Richardson, 5 Feb 2024
https://www.linkedin.com/posts/richardsonalexis_hi-everyone-...
If the project has legs, it's now under CNCF.
Re: Almost every infrastructure decision I endorse or regret
#57Earlier quoted context omitted.
We moved from Trello to Linear and it's been fantastic. I hope to never work at an organisation large enough for JIRA to be a good idea.
Newer (aka next gen aka Team-managed) Jira projects are pretty solid.
Do jira pages still take 30 seconds to load, and have all the interaction speed of cold molasses?
Does it have nice keyboard shortcuts yet?
Do I still need to perform an arcane ritual of setup to get the ticket statuses to be what I want?
Linear has been such a breath of fresh air, with such a solid desktop app (on Mac OS) that I don’t ever want to go back. Stuff happens instantly, the layout and semantics are an excellent “90% good enough” that I would happily relegate jira to only the most enterprise of enterprise projects.
Re: Almost every infrastructure decision I endorse or regret
#58[flagged]
Re: Almost every infrastructure decision I endorse or regret
#59The kitchen sink database used by everybody is such a common problem, yet it is repeated over and over again. If you grow it becomes significant tech debt and a performance bottleneck. Fortunately, with managed DBs like RDS it is really easy to run individual DB clusters per major app.
Lots of interesting comments on this one. Anyone have any good resources for learning how not to fuck up schema/db design for those of us who will probably never have a DBA on the team?
Re: Almost every infrastructure decision I endorse or regret
#60Great post. I do wonder - what are the simplest K8s alternatives?
Many say in the database world, "use Postgres", or "use sqlite." Similarly there are those databases that are robust that no one has heard of, but are very limited like FoundationDB. Or things that are specialized and generally respected like Clickhouse.
What are the equivalents of above for Kubernetes?