#mkdevWeeklyHighlight
There are new types of DNS records that are already implemented in most browsers and mobile clients and offer improvements to performance and security. This explains these new records by providing good examples on how they work:

https://www.domaintools.com/resources/blog/the-use-cases-and-benefits-of-svcb-and-https-dns-record-types/

#mkdevWeeklyHighlight
Dotan Horovits explains new standard for defining cloud costs and usage, and why we need this: https://horovits.medium.com/open-standards-in-finops-the-key-to-understanding-cloud-cost-6e30069f33a0

#mkdevWeeklyHighlight
Yearly report on the state of DevOps is out! Curious results regarding AI - it's too early to make any conclusions, but the current status is nevertheless important to keep an eye on: https://services.google.com/fh/files/misc/2023_final_report_sodr.pdf

#mkdevWeeklyHighlight
On one side, it’s sad to lose the only DB that actually scales to 0. On the other side, it’s good that the confusion around two simultaneously developed versions with different feature sets is finally gone. And v2 is actually great anyway! https://www.infoq.com/news/2024/01/aurora-serverless-v1-retirement/

#mkdevWeeklyHighlight
Practical advise here is mostly focused around DataDog features, but this article will be useful for any setup suffering from noisy alerts: https://www.datadoghq.com/blog/best-practices-to-prevent-alert-fatigue/

#mkdevWeeklyHighlight
Slack's journey to fully automated deployments - and how anomaly detection helps them to do that safely: https://slack.engineering/the-scary-thing-about-automating-deploys/

#mkdevWeeklyHighlight
Mozilla's open source project that simplifies running LLMs not unlike Docker simplified running containers: https://github.com/Mozilla-Ocho/llamafile

#mkdevWeeklyHighlight
Overview of the many downsides of CDK. All stem from the same root cause: behind the scenes, it's just CloudFormation, with all it's flaws: https://sst.dev/blog/moving-away-from-cdk

#mkdevWeeklyHighlight
We rarely see companies sharing their experience with technology over a long enough period of time to make this experience relevant. Jack Lindamood shared how all decisions played out over 4 years period, and it's just a treasure chest of good and simple decisions, many if not most of which mkdev endorses: https://cep.dev/posts/every-infrastructure-decision-i-endorse-or-regret-after-4-years-running-infrastructure-at-a-startup/

#mkdevWeeklyHighlight
It's been a while since we posted anything around the term SRE. This article gives 4 main archetypes of SRE professionals, as well as explaining why DevOps is not one of them: https://blog.alexewerlof.com/p/sre-archetypes

#mkdevWeeklyHighlight
A lovely idea of having an extremely simple global dashboard that, when problem occurs, can lead to a smaller and smaller specific dashboards: https://medium.com/site-reliability-engineering-leadership/the-single-pain-of-glass-6e42930e966

#mkdevWeeklyHighlight
Every once in a while you need to write a new small http service, and more often than not Go is an excellent choice. This article is a treasure of information on how to do that properly, backed by years of experience in the field: https://grafana.com/blog/2024/02/09/how-i-write-http-services-in-go-after-13-years/

#mkdevWeeklyHighlight
For many, this article will also be a moment of learning that IAM roles can have paths and slashes in general: https://aws.amazon.com/de/blogs/security/how-to-enforce-creation-of-roles-in-a-specific-path-use-iam-role-naming-in-hierarchy-models/

#mkdevWeeklyHighlight
An excellent overview of SLA, SLO and SLIs and what's involved in having any of those: https://uptimerobot.com/blog/sla-slo-sli/

#mkdevWeeklyHighlight
Resilience is all about getting ready for the future problems that might never occur (also thanks to being ready). This article attempts to justify why it's important to invest time into increasing resilience: https://willgallego.com/2024/02/16/justifying-resilience-work/

#mkdevWeeklyHighlight
Great examples of leveraging Storage Lens for FinOps processes. For organizations heavy on S3 storage, this can provide a few insights on potential cost savings: https://aws.amazon.com/blogs/storage/doordash-saves-millions-annually-using-amazon-s3-storage-lens/

#mkdevWeeklyHighlight
DORA metrics are an excellent way to track how your organization ships software and reacts to incidents. Like many things, they can also be misused. The article explains what’s the right angle to look at them: https://thenewstack.io/the-wrong-way-to-use-dora-metrics/

#mkdevWeeklyHighlight
A massive overview of all important bits around securing your GCP infrastructure. An excellent starting point if you're working with GCP for the first time and not entirely sure what is involved in protecting this environment: https://medium.com/@williamwarley/fortifying-the-cloud-mastering-security-on-google-cloud-platform-a-complete-guide-6c831bbe8ad4

#mkdevWeeklyHighlight
A number of practical tips on reducing alert fatigue. The best one is to treat each alert as an incident, as this is the only way to properly process them and configure towards less noise and more signal: https://incident.io/hubs/on-call/dealing-with-alert-fatigue-head-on

#mkdevWeeklyHighlight
AWS recognizes that not every organization needs the same security baseline. This one is focusing on startups, and provides a minimum required to stay secure, but keeps shipping fast: https://docs.aws.amazon.com/prescriptive-guidance/latest/aws-startup-security-baseline/welcome.html