Home / Companies / Momento / Blog / April 2024

April 2024 Summaries

4 posts from Momento

Filter
Month: Year:
Post Summaries Back to Blog
Serverless architecture offers a pathway to genuine agility for businesses by eliminating traditional infrastructure constraints, thus enabling faster innovation and delivery of customer value. To successfully adopt a serverless approach, organizations must evaluate their cultural commitment to agility, ensuring they can embrace rapid change and empower autonomous teams. Observability, crucial for managing the ephemeral and event-driven nature of serverless systems, requires a focus on logs, traces, and metrics to prevent lost signals and ensure reliable operations. Additionally, the existing skill set and curiosity of the team are pivotal, as serverless technologies compress job responsibilities and necessitate a willingness to adapt and learn new paradigms. This transformation extends beyond technology adoption to a mindset shift, challenging enterprises to assess their readiness for the agility serverless enables.
Apr 30, 2024 759 words in the original blog post.
Facing critical connection timeouts during load tests with AWS Lambda in VPCs, a Momento customer uncovered underlying networking limitations impacting their serverless architecture. The investigation revealed that the combination of NAT Gateways and Lambda's Hyperplane Elastic Network Interfaces (ENIs) were unable to handle the high-concurrency demands, leading to timed-out connections. Despite internal load tests showing no issues, the customer's architecture, which involved a Lambda function in a VPC connecting to Momento via a NAT Gateway, experienced bottlenecks due to the NAT Gateway’s connection limits and the ENI’s capacity constraints. To resolve these issues, it was recommended to increase network capacity by provisioning additional elastic IPs on the NAT Gateway and adding private subnets to the VPC, thus expanding the capacity for concurrent connections. The process highlighted the importance of careful network capacity planning for high-concurrency scenarios and suggested considering running Lambda outside of a VPC or utilizing PrivateLink to bypass such limitations, with Momento offering a robust solution for connection re-use in Lambda environments.
Apr 23, 2024 944 words in the original blog post.
Serverless computing offers enterprises a way to expedite software delivery while maintaining quality and agility by abstracting the provisioning and maintenance of infrastructure, thus allowing costs to scale predictably with usage and offering high availability. Serverless encompasses more than just compute services like AWS Lambda or Microsoft Azure Functions, as it includes components for data management, event handling, and API gateways, enabling modular and adaptable architectures. Transitioning to serverless requires investment in people, as it changes job roles and fosters faster experimentation by reducing reliance on infrastructure. Enterprises can begin their serverless journey by focusing on new features or extending existing applications, using tools like Lambda, API Gateway, and DynamoDB to add functionality without disrupting existing systems. Starting small and cultivating a culture of experimentation are key to successfully integrating serverless solutions at scale.
Apr 13, 2024 1,162 words in the original blog post.
Momento Cache introduces an innovative approach to caching for applications using MongoDB Atlas by extending the Mongoose ODM to automate caching processes without requiring code refactoring, significantly reducing latency. By integrating this caching with just one additional line of code, queries to MongoDB first check the Momento Cache, fetching from the database only if necessary, and then store the results for future use. This method, demonstrated in a Lambda function, showed that cached queries achieved an average latency of 2.8ms, a third of the 9.2ms latency observed with uncached MongoDB Atlas, highlighting the efficiency of this seamless caching solution.
Apr 07, 2024 497 words in the original blog post.