The conversation

Business & incomeExperience excerpt · English

Overall our setup doesn't come close to the setup I worked on at my last employer, but I have to …

… Overall our setup doesn't come close to the setup I worked on at my last employer, but I have to balance time spent on devops infra with time spent on the product, and that setup took ~5 full time engineers to maintain.

Original discussionAsk HN: Startup Devs -What's your biggest pain while managing cloud deployments?92 source comments · at import
2

What was this responding to?

Parent context · original excerpt

TJ

When you're a tiny team of developers working on something beyond MVP level and beyond heroku — managing your CI, deployments/rollbacks, DBs etc. looks like a nightmare to me without Devops expertise. I want to understand what kind of challenges you all are facing with regards to this. And any tools, practices, you’ll are using to reduce this pain? Ex- How do you deploy resources? How do you define architecture? How do you manage your environments, observability?, etc.

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

MD

> but there's some amount of extra stuff deployed (ingress controller, for example) that is documented in a text file Out of curiosity, why just the "readmeware" for those components? I can't think of a single thing that requires clickops in a modern k8s setup, so much so that in the beginning we used to bring up the full stack from nothing based on a single CFN template - roles, load balancer, auto-scaling group, control plane, csi driver (this was back when EKS was a raging tire fire ), and then lay the actual business apps on it. The whole process took about 8 minutes from go If nothing else, one will want to be cautious about readmeware components in disaster recovery situations. If no one has run those steps in 6 months, and then there's some kind of "all hands on deck," the stress will likely make that institutional knowledge leak out of their ears

Full original
TJ

> We don't need to deploy environments super often, so just do it manually and update documentation in the process if any variations are needed. So you don't need to deploy multiple times or you don't do it because the system is stable when you deploy less often? I mean is it by choice or because of some tool or expertise limitation? > Also, for architecture stored in text files - does that cause any problems for you?

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.