Need advice about which tool to choose?Ask the StackShare community!
LambCI vs wercker: What are the differences?
Developers describe LambCI as "A continuous integration system built on AWS Lambda". LambCI is a package you can upload to AWS Lambda that gets triggered when you push new code or open pull requests on GitHub and runs your tests (in the Lambda environment itself) – in the same vein as Jenkins, Travis or CircleCI. On the other hand, wercker is detailed as "Build, test, and deploy container-native applications". Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
LambCI and wercker can be primarily classified as "Continuous Integration" tools.
LambCI is an open source tool with 3.6K GitHub stars and 210 GitHub forks. Here's a link to LambCI's open source repository on GitHub.
We migrated all our CI/CD pipelines to CircleCI back in 2017 and are particularly happy about it since!
Our top loved feature is unlimited parallelism. We can run as many builds concurrently as we want.
We also use orbs, pipeline parameters, reusable commands, build cache, test insights.
For some of the heavier repos, we use a larger resource class and mount RAMdisk to a file system to speed up builds.
Pros of LambCI
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1
