When assessing the two solutions, reviewers found AWS Lambda easier to use, set up, and administer. Reviewers also preferred doing business with AWS Lambda overall.
It can help us to trigger the services and make the execution process faster.
Cost/performance ratio is not useful for our use case, which is a shame because on paper it should be a poster-child for Lambda.
Kubernetes is a sweet spot between flexibility and simplicity. Especially service discovery is made very simple. Competitors often are either to simple (Docker compose, swarm, fleet) or too complex (Marathon). Once it is up and running, low-level...
It's extremely immature (very buggy), the networking is just...painful, the scheduler is dumb and slow; those are my technical dislikes. My personal dislike is the overall lack of cohesive documentation as well as the assertion that just because there...
It can help us to trigger the services and make the execution process faster.
Kubernetes is a sweet spot between flexibility and simplicity. Especially service discovery is made very simple. Competitors often are either to simple (Docker compose, swarm, fleet) or too complex (Marathon). Once it is up and running, low-level...
Cost/performance ratio is not useful for our use case, which is a shame because on paper it should be a poster-child for Lambda.
It's extremely immature (very buggy), the networking is just...painful, the scheduler is dumb and slow; those are my technical dislikes. My personal dislike is the overall lack of cohesive documentation as well as the assertion that just because there...