From Code to Cloud: Turbocharging your Java Apps for AWS December 10th 2024 San Francisco

Anca Ghenade - Developer Advocate - [email protected] @tinyg210 @tinyg210.bsky.social

How does one go around developing applications using AWS services?

A Little Story About Cloud Development (freshly confirmed at AWS re:Invent)

1. The Software Engineers are tasked with developing a new application on AWS Cloud

2. Developing on a local machine, they soon find out that there are lots of dependencies with resources in the cloud

3. They realize that the dev & test loop is extremely slow and tedious. Every local change needs to be packaged and uploaded to the cloud for testing.

4. Now someone has a red build on their feature branch, but can’t efficiently test and debug their code in the CI/CD pipeline.

5. The whole team is using Git flow for development - one CI build per feature branch. There is an explosion of different environments required for development (branches x developers).

6. The manager approaches the team and complains that AWS dev/test resources are not being cleaned up properly causing cost spikes.

So things are kind of… complicated. 󰤆

And I have proof:

No content

5 minutes later…

What is LocalStack and how can it help you? A fully functional local cloud stack that was born out of these exact concerns.

● Enables a highly efficient dev & test loop for cloud apps ● Ships as a Docker image, easy to install and start up ● Support for 100 (-ish) services (and growing): ○ compute (Lambda, ECS, EKS) ○ various databases (DynamoDB, RDS) ○ messaging (SQS, Kinesis, MSK) ○ some sophisticated/exotic APIs (Athena, Glue) ● CI integrations & advanced collaboration features ● Branching out into other areas: Chaos Engineering, IAM Security Testing, Cloud Ephemeral Environments, 3rd Party Extensions, etc

No content

Let’s find a solution for each and every one of those issues and move fast to get to our goal.

No content

https://github.com/tinyg210/sf-java-meetup-demo

Number 1: Development (Follow the instructions in the README file, using terraform-local + “dev” profile)

No content

Using Spring Profiles…

Production Development + Testing

Production Everything before production

“Your application won’t even know the difference”

Number 2: Testing IaC

Two ways of doing that: ● Manually testing while developing 👆 ● Along with your code tests using Testcontainers 👇

Number 3: Testing Code Please use this repo for this use-case: https://github.com/tinyg210/terraform-testcontainers-shipmen t-list-demo (It’s the same project, without generating random bucket names - for ease of use)

No content

No content

Testing your application workflow

No content

Your local tests…

Number 4: CI/CD Integration (tests, image builds, deployments, etc) (File: .github/workflows/ci.yml)

● Automated Testing ● Continuous Deployment ● Integration Testing ● Code Quality Analysis ● Infrastructure as Code (IaC) Validation ● Containerization and Orchestration ● Feature Branch Testing ● Rollbacks and Blue/Green Deployments ● Performance Testing and Scalability ● Automated Documentation Generation

● Automated Testing ● Continuous Deployment ● Integration Testing ● Code Quality Analysis ● Infrastructure as Code (IaC) Validation ● Containerization and Orchestration ● Feature Branch Testing ● Rollbacks and Blue/Green Deployments ● Performance Testing and Scalability ● Automated Documentation Generation

No content

Number 5: PR Preview & final checks (.github/workflows/ci.yml) When the GitHub Actions pipeline runs successfully a snapshot (Cloud Pod) of the LocalStack instance is taken and used to create a remote instance, which will have the connection URL displayed after creation.

Number 6: Deployment to AWS Run the backend using the profile “prod” + use Terraform with the same main.tf file.

We’re giving the OPS back to the DEVS.

Thank You