Could kept infra as a code, logging, auth and so on in packages, gRPC or message queues for communication, telemetry, monitoring/alerts and more stuff as a code too... got to the point creating new service was just new…
Was in startup which quit before hitting 1000 users in app at the same time, but performance was top priority so data layer stack was quiet big.
Was in org with 10 people devops dedicated team, it was smooth, also as a dev could push requests for their repos... but also only 3 devops and they were so busy my requirement for basic stuff was burried in backlog.…
From my experience, microservices were great if there are more devs, organizational advantage over tech. CI/CD - infra can be as code, shared across, K8s port-forward for local development, better resource utilization,…
Could kept infra as a code, logging, auth and so on in packages, gRPC or message queues for communication, telemetry, monitoring/alerts and more stuff as a code too... got to the point creating new service was just new…
Was in startup which quit before hitting 1000 users in app at the same time, but performance was top priority so data layer stack was quiet big.
Was in org with 10 people devops dedicated team, it was smooth, also as a dev could push requests for their repos... but also only 3 devops and they were so busy my requirement for basic stuff was burried in backlog.…
From my experience, microservices were great if there are more devs, organizational advantage over tech. CI/CD - infra can be as code, shared across, K8s port-forward for local development, better resource utilization,…