BUILDING AND SHIPPING MICROSERVICES WITH GO, GRPC AND KUBERNETES

trust a platform, not tribal knowledge. k8s is that system.

writing microservices

know your resource requirements
health check
- liveness -> are you even alive, is the container up? if not, i'll restart you.
- readiness -> are you ready to receive traffic, can you talk to database, etc
resiliency
- assume database, anything over network, etc, will be flaky. not being able to talk to DB is not an exception, don't throw an exception.
use jobs as glue, not necessarily part of the app or running a fully formed web service
more stuff outside of the cluster? vault, spinnaker, etc
using proxies to abstract languages from containers
- rate limiting in ruby v java, do it in a sidecar