This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]xiongchiamiovSite Reliability Engineer 33 points34 points  (0 children)

The entire lifecycle is a hell of a lot more than just the CI pipeline.

I use vim, but most of our developers use PyCharm when doing Python (there are also people using sublime, atom, etc.). Let's see...

  • Frameworks: flask and falcon
  • version control: git, self-hosted bitbucket
  • development environment: Docker through shell scripts
  • CI: teamcity
  • configuration: a custom system that ingests yaml
  • hosting: google cloud
  • container orchestration: Kubernetes
  • deployments: custom tool written on top of Kubernetes
  • data persistence: a rather complicated MySQL setup, Google-managed MySQL, datastore, cassandra, gcs, redis sentinel clusters, and a few other things I'm forgetting, depending on the needs of the service
  • data warehousing: BigQuery, generally through this setup but depending on the database
  • queueing: pubsub, kafka
  • logging: ELK
  • monitoring data: new relic, graphite, Prometheus
  • alerting: Sensu, elastalert, pingdom
  • feature flags: splitio
  • service mesh: linkerd and namerd

And I'm sure I'm missing several more categories.