moshloop
Joined 7 years ago
Joined 7 years ago
Flanksource is building a next generation mission control platform that enables teams to communicate and coordinate around system health and incidents, by aggregating health, configuration, change, logs and traces into an application focused view.
Email me at moshe @ flanksource.com or apply here: https://www.flanksource.com/careers and mention HN
Flanksource is building a next generation mission control platform that enables teams to communicate and coordinate around system health and incidents.
Apply here: https://www.flanksource.com/careers and mention HN
We are currently in "stealth" mode building a test-driven incident response platform for enterprises - automating most of the mundane and frustrating work required in incident response.
To apply email [email protected] or via our careers page: https://www.flanksource.com/careers
The goal of Kubernetes is to improve the portability of people by introducing abstraction layers at the infrastructure layer - These abstractions can seem overly complex, but they are essential to meet the needs of all users (developers, operators, cloud providers, etc)
Before kubernetes in order for a developer to deploy an application they would need to (send email, create terraform/cloudformation, run some commands, create ticket for loadbalancer team, etc) - these steps would rarely be same between companies or even between different teams in the same company.
After kubernetes you write a Deployment spec, and knowing how to write a deployment spec is portable to the next job. Sure there are many tools that introduce opinionated workflows over the essentially verbose configuration of base Kubernetes objects, and yes your next job may not use them, but understanding the building blocks, still make it faster than if every new company / team did everything completely differently.
If you only have a single team/application with limited employee churn - then the benefits may not outweigh the increased complexity.
Flanksource is building a test-driven incident response platform that enables teams to communicate effectively through real-time system models, reducing the broken telephone, "Please re-test" feedback loops that plague organizations with multiple teams.
Apply at https://www.flanksource.com/careers or reach out to me: moshe at flanksource.com, mentioning HN in the subject line.
We are looking for full-time, part-time and weekend warriors to help us with R&D and some project based work.
Email me @ moshe at flanksource.com
Flanksource is hiring for AWS and Kubernetes Site Reliability Engineers we are remote first since inception with a strong focus on open-source - both from a technology perspective and a way of working.
Email me @ moshe at flanksource.com
We are looking for seasoned engineers with a passion for Open Source, particularly Kubernetes and Go
https://www.flanksource.com/careers/site-reliability-enginee...
or dm me on the Kubernetes slack
We are looking for strong engineers to join our remote, fully distributed team to help us build a management plane to cater for Kubernetes as the OS for the Datacenter/Enterprise.
Apply here: https://www.flanksource.com/careers/site-reliability-enginee...
We are a Kubernetes company focused on accelerating large enterprises on their cloud-native journey.
https://www.flanksource.com/careers/site-reliability-enginee...
Kubernetes works with fully-fledged VM's as well - See Kubevirt
Both fundamentally are about abstracting the way in which infrastructure is managed.
Getting this to perform well required several optimizations at both the Go and Postgres levels. On the Go side, we use prioritized work queues, event de-duplication, and even switched to Rust for efficient JSON diffs. For Postgres, we leverage materialized views and trigger-based optimistic locking