From Code to Cloud: Turbocharging your Java Apps for AWS

Slides for the presentation at the JUG SF on Dec 11th 2024

Transcript

1. From Code to Cloud: Turbocharging your Java Apps for AWS December 10th 2024 San Francisco
2. Anca Ghenade - Developer Advocate - anca.ghenade@localstack.cloud @tinyg210 @tinyg210.bsky.social
3. How does one go around developing applications using AWS services?
4. A Little Story About Cloud Development (freshly confirmed at AWS re:Invent)
5. 1. The Software Engineers are tasked with developing a new application on AWS Cloud
6. 2. Developing on a local machine, they soon find out that there are lots of dependencies with resources in the cloud
7. 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.
8. 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.
9. 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).
10. 6. The manager approaches the team and complains that AWS dev/test resources are not being cleaned up properly causing cost spikes.
11. So things are kind of… complicated. 󰤆
12. And I have proof:
14. 5 minutes later…
15. What is LocalStack and how can it help you? A fully functional local cloud stack that was born out of these exact concerns.
16. • 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
18. Let’s find a solution for each and every one of those issues and move fast to get to our goal.
20. https://github.com/tinyg210/sf-java-meetup-demo
21. Number 1: Development (Follow the instructions in the README file, using terraform-local + “dev” profile)
23. Using Spring Profiles…
24. Production Development + Testing
25. Production Everything before production
26. “Your application won’t even know the difference”
27. Number 2: Testing IaC
28. Two ways of doing that: • Manually testing while developing 👆 • Along with your code tests using Testcontainers 👇
29. 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)
32. Testing your application workflow
34. Your local tests…
35. Number 4: CI/CD Integration (tests, image builds, deployments, etc) (File: .github/workflows/ci.yml)
36. • 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
37. • 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
39. 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.
40. Number 6: Deployment to AWS Run the backend using the profile “prod” + use Terraform with the same main.tf file.
41. We’re giving the OPS back to the DEVS.
42. Thank You