Using serverless applications comes with many advantages, such as a quicker time to release, automatic scaling of applications, and flexibility. However, when users migrate to serverless, they discover the challenges that come from the result of old developer habits no longer being available. One of the strongest challenges is debugging. Debugging allows developers to find the origin of any issue and solve it. On a daily basis, developers need to debug their applications on their local IDE, but this isn’t possible in serverless applications. That’s where Thundra comes in. Thundra Debugger eases this pain by offering a remote debugging experience on your local IDE.
To start using Thundra Debugger, sign up and select “Thundra Debugger” during the onboarding process.
You need to build a connection through an authentication key between the Lambda function and your local IDE to debug your Lambda function. This authentication is established with the Thundra Authentication Key. After you select “Thundra Debugger,” the authentication key will be available for your account.
If you've already signed up for Thundra, you can find your authentication key on the Settings page.
We currently support Java, Python, and Node.js runtimes for debugging. Follow the instructions to have a native debugging experience for your Lambda functions:
To ease your debugging experience, VSCode and IntelliJ Idea plugins are available on marketplaces: