4 ms·
I don't know how the author can claim that they run a "simple" architecture. From their job pages: Our stack : backend: Python 3 (+ mypy) API layer:
by wackget 5y ago
I don't know how the author can claim that they run a "simple" architecture.
From their job pages:
Our stack :
backend: Python 3 (+ mypy)
API layer: GraphQL
android frontend: Kotlin/Jetpack
iOS frontend: Swift/SwiftUI
web frontend: TypeScript/React
database: Postgres
infrastructure: GCP / Terraform
orchestration: Kubernetes
That is not simple by any stretch of the imagination.
- rendall 5y agoHow would you simplify this?
- nunez 5y agofor starters i wouldnt use kubernetes. love the system, but boy is it complicated. i'd use a few cloud function or stick them in VMs behind a load balancer and call it good.
- polio 5y ago> As for Kubernetes, we use Kubernetes because knew that, if the business was successful (which it has been) and we kept expanding, we’d eventually expand to countries that require us operate our services in country. The exact regulations vary by country, but we’re already expanding into one major African market that requires we operate our “primary datacenter” in the country and there are others with regulations that, e.g., require us to be able to fail over to a datacenter in the country.
- deleted 5y ago[deleted]