https://github.com/lambdify/lambdify-aws-events
Lightweight version of the entities that represents AWS Events.
https://github.com/lambdify/lambdify-aws-events
aws aws-lambda aws-sdk java8 kotlin serverless
Last synced: 2 months ago
JSON representation
Lightweight version of the entities that represents AWS Events.
- Host: GitHub
- URL: https://github.com/lambdify/lambdify-aws-events
- Owner: lambdify
- Created: 2018-06-04T19:22:05.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2019-04-23T09:34:16.000Z (almost 7 years ago)
- Last Synced: 2025-03-01T00:37:05.163Z (about 1 year ago)
- Topics: aws, aws-lambda, aws-sdk, java8, kotlin, serverless
- Language: Java
- Homepage:
- Size: 39.1 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## AWS Java Lightweight Events
Lightweight version of the entities that represents AWS Events.
## Why another AWS Lambda API?
Amazon Web Services used to have a standard API which depends on a set of third-party libraries to make their
development routine easier. Although it is a great solution and works very well, due to the nature of how AWS Lambda
loads your functions, it may lead to long cold starts.
This set of entities were designed to have _no dependencies at all_, ensuring you will have a very
lightweight zip to deploy your functions.
## Reporting Bugs/Feature Requests
We welcome you to use the GitHub issue tracker to report bugs or suggest features.
When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
* A reproducible test case or series of steps
* The version of our code being used
* Any modifications you've made relevant to the bug
* Anything unusual about your environment or deployment
## Contributing via Pull Requests
Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
1. You are working against the latest source on the *master* branch.
2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
To send us a pull request, please:
1. Fork the repository.
2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
3. Ensure local tests pass.
4. Commit to your fork using clear commit messages.
5. Send us a pull request, answering any default questions in the pull request interface.
6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
## Finding contributions to work on
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
## License
All open source libraries developed by Lambdify are licenced under the Apache License 2 terms.