Using AWS Lambda for Data ETL
Anonymous | TrustRadius Reviewer
Updated June 13, 2019

Using AWS Lambda for Data ETL

Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with AWS Lambda

AWS Lambda is mostly being used to run our hourly/daily cron jobs. It is used across the entire organization. It helped us move data between external and internal data sources to the appropriate destinations.
  • Easy to set up.
  • Support different programming languages.
  • Events-based trigger.
  • Continuous deployment integration with GitHub.
  • Would like to easily toggle between environments.
  • An interface to map out/organize different functions.
  • AWS Lambda allows us to migrate off our 3rd Party ETL platform, reducing costs by 80% (no longer paying for licensing fee and server cost).
  • It allows us to outsource independent functions to contractors and easily integrate this back into our core process.
While AWS Lambda doesn't have the UI or the predefined functions that these other services provide, what was apparent to us is the cost saving and flexibility we have with AWS Lambda once we have it set up.
AWS Lambda allows us to develop certain process without setting up a server. I would recommend AWS Lambda for a process that doesn't need to be real-time or needs to be always on.

AWS Lambda Feature Ratings

Ease of building user interfaces
7
Scalability
9
Platform management overhead
5
Platform access control
9
Services-enabled integration
7
Development environment creation
3
Development environment replication
3
Issue monitoring and notification
5
Issue recovery
5
Upgrades and platform fixes
8