Seamlessly build, deploy & manage cloud-native serverless applications!
Jazz, a serverless platform, accelerates adoption of serverless technology within your enterprise. Jazz comes with a beautiful UI that lets developers quickly create serverless applications with a click of a button. Its modular design makes it easy to add new integrations.
- Services - As of today, Jazz can help build functions, APIs and static websites. Fully customizable template-based design makes it easy to define new ones and expose them as services to the developers.
- Deployment Targets - Currently Jazz can deploy to AWS managed services like (Lambda, API Gateway, S3, CloudFront etc.). We plan to support related services in Azure and GCP in the near future.
- Deployment & CI/CD - Jazz comes with CI/CD by default. It creates a code repository per service and adds a web hook to trigger build/deployment workflows whenever it sees a commit. We leverage Jenkins open source for build process and Serverless Framework for deploying these services.
- Other Features - Other useful features/integrations like SCM (Gitlab/Bitbucket), monitoring (CloudWatch), logging (ElasticSearch), authentication (Cognito), code quality metrics (SonarQube) comes with Jazz by default.
- Extensions - Jazz is designed to integrate and work well with other systems that your enterprise needs. You can check out our optional extensions like Slack, Splunk etc. Centralized configuration helps Jazz admins to easily enable/disable these features as per their needs.
Jazz is open-sourced and under active development by T-Mobile's Cloud Center of Excellence.
For complete user guide, see our wiki.
Following is the high level logical architecture of Jazz.
You can install Jazz in your AWS account using the automated installer.
You can try out public preview version of Jazz by registering with your email address here. You will need a registration code which can be requested by joining slack.
- Breaking/nontrivial features first go into named feature branches cut from
develop - When/if a feature branch is chosen to be included in the next release, it is merged into
develop - Release testing happens in
develop - When confirmed/vetted,
developis merged intomaster, andmasterbecomes the current release. - Small fixes explicitly intended for the next release can be PRed directly into
developwithout first needing a feature branch.
tl;dr master is always the current release, develop is always the current state of the next release. If you want to contribute a PR, we recommend you fork and work in a branch off of develop, then PR against develop. Project owners will move you into a feature branch if they deem it necessary.
Jazz is released under the Apache 2.0 License