4 ms·

Microservices doesn't necessarily mean K8S running on self-managed compute instances as in the example given in the article. The main mistake of the article is

Microservices doesn't necessarily mean K8S running on self-managed compute instances as in the example given in the article. The main mistake of the article is that the premise is "microservices" but then the examples are about infrastructure (K8S etc), but the 2 things are not tied, you can have that same architecture cited in the article running monolith instances for example, and it would be every bit as complex as managing the micorservices example, without any of the advantages. Fully managed serverless solutions like Lambda/Cloudflare Workers/etc, managed through SAM or Serverless Framework solves most of the problems cited in the article. The whole infra in our case is API Gateway + Lambda + DynamoDB, this infra is not more complex to manage than our old monolith which was on ALB + EC2 + RDS. Deployment is one "sam deploy" away (done in Github Actions), this is actually even simpler than our previous monolith.

tabtab 5y ago
"Microservice" is inconsistently defined. One cannot accuse them of using a strawman definition if there is no realman.
- mastazi 5y ago
  I disagree, microservices are an architectural concept related to the software, not to the infrastructure. Whether you are using containers or VPS or serverless or bare metal for your infrastructure, that's completely unrelated to the concept of microservices: you can deploy either a monolith or microservices in any of the above. As an example you can deploy a monolith on Lambda[1] or you can deploy microservices on bare metal using one of the several self managed serverless engines available[2]. [1] see e.g. https://claudiajs.com/tutorials/serverless-express.html https://claudiajs.com/tutorials/serverless-express.html or https://blog.logrocket.com/zappa-and-aws-lambda-for-serverless-django/ https://blog.logrocket.com/zappa-and-aws-lambda-for-serverle... [2] see e.g. https://fnproject.io/ https://fnproject.io/ and https://knative.dev/ https://knative.dev/

tabtab 5y ago

"Microservice" is inconsistently defined. One cannot accuse them of using a strawman definition if there is no realman.

mastazi 5y ago
I disagree, microservices are an architectural concept related to the software, not to the infrastructure. Whether you are using containers or VPS or serverless or bare metal for your infrastructure, that's completely unrelated to the concept of microservices: you can deploy either a monolith or microservices in any of the above. As an example you can deploy a monolith on Lambda[1] or you can deploy microservices on bare metal using one of the several self managed serverless engines available[2]. [1] see e.g. https://claudiajs.com/tutorials/serverless-express.html https://claudiajs.com/tutorials/serverless-express.html or https://blog.logrocket.com/zappa-and-aws-lambda-for-serverless-django/ https://blog.logrocket.com/zappa-and-aws-lambda-for-serverle... [2] see e.g. https://fnproject.io/ https://fnproject.io/ and https://knative.dev/ https://knative.dev/