Create accountLogin

Recent searches

No recent searches

Search options

Not available on lingo.lol.
lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Administered by:

Server stats:

64
active users

lingo.lol: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.9

#PlatformEngineering

1 post1 participant0 posts today
Public
Ariel

Kubernetes curly: deployment with autoscaling, each pod depends on and occasionally writes-to an external database.
To minimise database reads, an in-memory cache is implemented in the application.

However, when a pod writes to the database it should invalidate that key in the cache for all pods.
This works fine for the local cache, but how to distribute that invalidation?

I suppose we could use a statefulset and then hit the service for each other running pod but that seems... messy.

3 pods with local caches hitting a db
#Kubernetes#k8s#PlatformEngineering
Public
Ariel

> When we talk about how to design our infrastructure code, we start with the limitations of our tooling and try to derive what we can do within those constraints and then call that best practice.

~ Malcolm Matalka

pid1.dev/posts/terralith/

pid1 · Terralith: The Terraform and OpenTofu BoogiemanTerrateam has a very expressive configuration file. We need it because, as any Terraform or Tofu user knows, there is no standard on how you should design your repository. The Eternal September question of r/terraform is asking how to structure a repository for multiple environments. It comes up so much that we even wrote a blog post about it. Terraform and Tofu users, in my experience, are especially concerned with how to structure a repository. I think this is because Tofu is so low-level. It concerns itself with how to manage the specific resources within your infrastructure but not really your infrastructure as a whole. Tofu manages a state file, which is how it connects the code you write to the actual infrastructure in the cloud. Each directory that has a state file associated with it is called a root module. You run the Tofu program in a root module and it evaluates everything.
#Terraform#Terragrunt#IaC
Public
Nick

Failure must be an option in any innovative environment. This doesn’t mean that failure should be the goal, but rather that it should be accepted as a possible outcome. By doing so, teams can experiment, take risks, and ultimately find novel solutions to complex problems.

nickperkins.au/article/failure

Nick Perkins · Failure MUST be an option for innovationThis week I hosted a brown bag session at work where I explored the idea that failure isn’t something to be avoided at all costs but must be a safe option for software engineering teams. The concept of failure often carries a negative connotation. However, embracing failure as an option can foster an environment of learning, innovation, and psychological safety. Let’s explore this by looking at the benefits this shift in mindset can bring, and the elements required to create a culture where failure is seen as a stepping stone to success.
#DevOps#PlatformEngineering
Public
Terra Field

Hey #PlatformEngineering folks (especially with Kafka experience!) - how would you like to be the new Terra at @honeycombio? They are hiring a Staff Platform Engineer to backfill for me (my last day is Friday) and you couldn’t ask for a better group of folks.

jobs.lever.co/honeycomb/4f2ae4

jobs.lever.coHoneycomb - Staff Platform EngineerWhat We’re Building Honeycomb is the observability platform for teams who manage software that matters. Send any data to our one-of-a-kind data store, solve problems with all the relevant context, and fix issues before your customers find them. Honeycomb is the unified, fast, and collaborative choice for engineering teams who care about customer experience to get the answers they need, quickly. We are passionate about consumer-quality developer tools and excited to build technology that raises our industry’s expectations of what our tools can do for us. We’re working with well known companies like HelloFresh, Slack, LaunchDarkly, and Vanguard and more across a range of industries. This is an exciting time in our trajectory, as we’ve closed Series D funding, scaled past the 200-person mark, and were named to Forbes’ America’s Best Startups of 2022 and 2023! The Honeycomb product handles enormous amounts of data, and the Core Services team builds and manages all the internals that make
Public *
The Late Night Linux Family

If you're sick of all the election coverage (or just want a break), why not listen to our podcasts about Linux, open source, systems administration, development, cloud computing, and more?

Just search for Late Night Linux Family All Episodes in your podcast app, or paste the RSS feed in manually:

latenightlinux.com/feed/all

More details about our shows at latenightlinux.com/

Late Night Linux Family All Episodes in AntennaPod
#podcast#linux#opensource
Public
Jason Yip

"...both engineers and product managers mistake novelty as the most important offering their platforms can provide, and they forget that stability is often at least as important, if not more so."

Fournier, Camille; Nowland, Ian. #PlatformEngineering: A Guide for Technical, Product, and People Leaders (p. 203). O'Reilly Media. Kindle Edition.

Public
Sean Hood

Were you born to deploy #Kubernetes clusters? Do you for some reason enjoy using #Terraform? Then my team might have a job for you:

jobs.dayforcehcm.com/en-US/dis

TL;DR: Cloud Engineer III
EdTech Company
Remote anywhere in US (UK opening may have been filled)
Building out our idea of an internal platform
Working with Kubernetes, Terraform, #AWS, #Puppet, #Linux
Small distributed team of 6 scattered over almost as many timezones.
I don't know the salary :(

jobs.dayforcehcm.comJob Details | Dayforce JobsFind your next adventure
#devops#PlatformEngineering#getfedihired
ExploreLive feeds
About