Comparison of deploying Titiler in Lambda/Azure Functions vs EKS/AKS #1147
raster-blaster
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team 👋,
I’m currently evaluating deployment strategies for running Titiler in production and wanted to get insights from the community regarding best practices, cost efficiency, and performance tradeoffs.
I understand that the right deployment option often depends on request patterns and user traffic, but I’m curious to know:
💡 What are the advantages and disadvantages of running Titiler in:
• Serverless environments like AWS Lambda / Azure Functions
• Container orchestration platforms like EKS / AKS
🧩 Specific points I’m curious about:
• Cold start latency in serverless
• Cost-effectiveness at scale
• Popular patterns seen in production deployments (e.g., what are most people doing?)
• Any lessons learned that would help new users decide between these two models
This is a general architecture discussion to gather perspectives from Titiler users and contributors. I believe it could also be useful for others in the community making similar choices.
Thanks in advance! 🙏
Looking forward to your thoughts and experiences.
Beta Was this translation helpful? Give feedback.
All reactions