I joined a company where the backend relies on lambdas, leading to integration, development, and testing challenges plus vague project tickets and team roles. Is this design sound?
hey guys, im curious about how u handle updates in a lambda based backend. any experience with debugging chalenges or scaling when functions start to pile up? wonder if there’s a smoother way to keep it all in order
From practical experience, relying solely on lambdas for backend functionality is increasingly common, especially in microservices architectures where scalability and cost efficiency are prioritized. However, this approach can lead to integration and testing challenges if not designed with clear communication between functions. In my experience, careful planning in defining boundaries and responsibilities for each lambda is key. Additionally, incorporating proper orchestration and maintaining flexible development practices can help address potential issues that often arise from a design that lacks a broader contextual framework.
i think lambdas work fine if you keep a clear structure; issues usually come from poor planning not the tech itself. make sure testing and integation are nailed down early or else youll run into messy deploys.