Backend deployment: k8s vs lambda

[arkid15r]

Based on the #430 here is a summary of the pros and cons of using Kubernetes (k8s) versus AWS Lambda for deploying OWASP Nest:

Kubernetes:

Pros:

• Scalability and Flexibility: Kubernetes allows for granular control over scaling and deployment of containerized applications, making it suitable for complex, long-running, or high-traffic applications.
• Portability: Applications deployed on Kubernetes can be moved across different cloud providers or on-premises environments, reducing vendor lock-in.
• Ecosystem Integration: Kubernetes integrates well with various tools and services, providing a robust ecosystem for application management.

Cons:

• Complexity: Setting up and managing a Kubernetes cluster requires significant expertise and can introduce operational overhead.
• Resource Management: Requires manual provisioning and management of underlying infrastructure, which can lead to higher costs if not managed efficiently.
• Maintenance: Ongoing maintenance, including updates and security patches, is the responsibility of the user, necessitating a dedicated DevOps effort.

AWS Lambda:

Pros:

• Simplicity and Speed: Enables rapid deployment without the need to manage underlying servers, allowing developers to focus on code and business logic.
• Automatic Scaling: Automatically scales with the number of requests, handling variable workloads efficiently without manual intervention.
• Cost Efficiency: Operates on a pay-per-use model, which can be cost-effective for applications with sporadic or unpredictable workloads.

Cons:

• Execution Time Limits: AWS Lambda has a maximum execution duration (15 minutes as of now), which may not be suitable for long-running processes.
• Cold Start Latency: Functions may experience latency during initial invocation after a period of inactivity, potentially affecting performance.
• Vendor Lock-In: Tightly integrated with AWS services, making it challenging to migrate to other cloud providers without significant changes.

[yashpandey06]

Complex applications are handled well in case of k8s deployments ...so as the nest is already growing ,the k8s would be good to go !

[arkid15r]

It seems the vast majority voted for k8s based solution

Any new opinions on the Zappa vs k8s?

[yashgoyal0110]

@arkid15r Hey, I have quite decent experience with kubernetes

[Rajgupta36]

@arkid15r I've previously worked on deploying a Vite and Express-based app using Kubernetes. I implemented services, replica concept, and horizontal scaling with load balancing, all on the Vultr Cloud platform.

[Naveen-Pal]

I have a experience of using knative with kourier ingress on Kubernetes to make serverless flask portal

[abhayymishraa]

@arkid15r
what i think is k8s would be a better option than zappa (which is based on AWS lambda). Cold starts in serverless environments like lambda can add significant delays, especially after periods of inactivity, which can negatively impact user experience.
while,
k8s, on the other side, do not suffer from cold start issues because it keeps your containers running, so the application is always available and ready to handle requests. it is especially beneficial for applications that need consistent low-latency responses or for those that run long processes, where Lambda's execution time limits might also become a constraint.
i have worked with K8s on a project that involved using nginx for reverse proxying, and I found it to be a highly effective solution for managing complex, containerized applications.