[airhead969]

The biggest problems with microservices are the lack of injecting cross-cutting concerns like security, monitoring, circuit breakers, resource metering, alerting, service dependencies, logs, resource isolation, upgrading on-the-fly, migrations, backups/restores of data, and configuration. These all have to be handled.

Docker with k8s is awful when it comes to resource metering. Docker is terrible with security and resource isolation. K8s, in general, is awful IMO because of the way it was architected and implemented.

Xen-ified "containers" (regular VMs but managed) with an ability to inject uniform, templated, configured concerns is how to do services: micro or macro; ephemeral app, infrastructure, or backend. Also, backups and logs have to live somewhere else.

Basically, a APPaaS/PaaS/IaaS in the spirit of K8s + OpenStack but much cleaner, workable, easier, simpler, fewer choices, more usable, more reliable, less stupid, and more standardized. (Discovery is insecure and fundamentally unworkable; top-down provisioning knows exactly what exists and is alive so use that as the authoritative single-source-of-truth.)

There is no other way I can see.

[macando]

> but much cleaner, workable, easier, simpler, fewer choices, more usable, more reliable, less stupid, and more standardized.

You can say this about 80% of tech yet here we are.

[papito]

You can do circuit breakers with a monolith. "Release It!" is an excellent book that covers many patterns that do not involve the last resort of distributed systems.