AWS Lambda Reviews

LakeFS Reviews

AWS Lambda mentions (297)

• Serverless with Mama J — Why Serverless

  AWS Lambda is a service that runs your code without you managing any servers. You write your code, deploy it to Lambda, and it takes care of the infrastructure — servers, networking, security, and scaling. - Source: dev.to / 3 months ago

• Enriching Free Trial Signups: The PLG Data Stack for Turning Inbound Users Into Qualified Pipeline

  Clay can replace the Lambda and API chain if you'd rather avoid custom code. You set up a Clay table as the enrichment layer, trigger it from Segment via webhook, and it handles the waterfall and CRM push without writing a function. The tradeoff: less control over scoring logic and higher cost per enriched contact. - Source: dev.to / 2 months ago

• Dynamic Looping Comes to AWS SAM

  To show why this matters, take a look at the following example. I have three AWS Lambda functions, Lambda being the serverless compute service, that each handle a different endpoint on the same API. But, almost everything about them is the same. They have the same runtime, the same memory configuration, and nearly the same structure. The only differences are the name, handler, and possibly some environment variables. - Source: dev.to / 2 months ago

• AIP-C01 last-minute revision: exam traps, memory hooks, and quick notes

  Query Expansion and Decomposition: Amazon Bedrock query expansion broadens search; AWS Lambda query decomposition breaks complex queries into sub-queries; AWS Step Functions orchestrates multi-step retrieval. - Source: dev.to / 3 months ago

• Why AWS Certified GenAI Developer stands apart from other AWS certs

  You need to understand synchronous and asynchronous inference patterns, event-driven architectures using Amazon EventBridge, workflow orchestration with AWS Step Functions, data processing with AWS Lambda, state management with Amazon DynamoDB, and security with AWS Identity and Access Management (IAM). The exam tests your ability to design serverless architectures that scale automatically, handle failures... - Source: dev.to / 3 months ago

LakeFS mentions (6)

• Ask HN: AWS S3, Cloudflare R2, GCS, Wasabi, or B2?

  I would add https://github.com/gaul/s3proxy to your list. - Source: Hacker News / over 2 years ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  * data state - this is contents of both your data and metadata at a given point in time. if your data doesn't fit into a single database, this can be difficult to manage. We use this technology to help us: https://lakefs.io/. - Source: Hacker News / almost 3 years ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  Saltcured, find these comments super insightful! > Yeah, there's a lot of hidden magic/assumptions in having a "writable snapshot of a specific version" of production data. That's absolutely a huge assumption. This technology has been a game changer for us: https://lakefs.io/ > It becomes a headache when there is too much contention to use these sandboxes, or too much manual effort to reset them to a desired... - Source: Hacker News / almost 3 years ago

• Using git to version control experimental data (not code)?

  You should not store your data in git itself, but rather use git to version your data sets. The currently best option for that is (IMHO) https://lakefs.io though there are a few others in various states of usability/maturity. Source: over 3 years ago

• How are you incrementally testing your data pipelines as you develop them?

  I mean if you're ready to adopt a new framework into your ecosystem this is one of the major usecases for LakeFS. Source: over 3 years ago