What I learned when I started studying AWS as a Java developer
AWS from a Java developer's perspective
Starting to study cloud computing can seem complicated at first. There are many services, terms, and new concepts, and it is easy to get lost trying to figure out where to begin.
As a Systems Analysis and Development student and a developer focused on Java and Spring Boot, I decided to start studying AWS to better understand how backend applications run in real-world production environments.
One of the first things I realized is that learning AWS isn't just about learning how to use specific services. You also need to understand concepts like infrastructure, networking, security, scalability, and resource management.
Starting with the fundamentals
Before trying to use multiple services at once, I began by studying basic AWS concepts.
Some of the services that caught my attention the most were Amazon EC2 (for compute), Amazon RDS (for relational databases), and Amazon S3 (for object storage).
EC2 was particularly interesting to me because it helped me better understand the difference between running an application locally and running one on a cloud server.
Locally, I can launch a Spring Boot application via IntelliJ or the terminal and access it directly. In the cloud, I start dealing with additional concepts such as ports, security rules, IP addresses, environment variables, and server availability.
The connection to backend development
Since my main focus is backend development with Java, I began to view AWS as a natural extension of API development.
A Spring Boot application might work perfectly on my computer, but that is only part of the process.
In a real-world environment, we also need to consider questions like:
Where will the application run?
Where will the database be located?
How will the application be accessed over the internet?
How do we protect credentials?
How do we monitor the application?
How do we handle new deployments?
How do we deal with increased traffic?
These questions made me realize that software development and software operations involve different skill sets, yet they complement each other.
One of the most important things I learned
One of the concepts that most changed my perspective was understanding that the cloud doesn't simply mean "having a server online." AWS offers a wide range of services that can be combined to build complete architectures.
For instance, a backend application might use a compute service to run the application, a managed database to store information, and an object storage service for files.
Furthermore, there are services dedicated to security, monitoring, networking, messaging, and various other needs.
This demonstrates that learning cloud technology is a gradual process.
My next step
I am still at the beginning of this journey, but I intend to continue studying AWS and applying this knowledge to my Java and Spring Boot projects.
My goal is to move from an application that simply runs locally to one that can also run securely and reliably in the cloud.
I believe the best way to learn is through practice. That is why I want to keep creating small projects, deploying them, troubleshooting errors, and understanding how each AWS service can solve real-world problems.
Conclusion
Studying AWS as a backend developer has helped me view software development from a more comprehensive perspective.
I still have a lot to learn, but I believe that starting with the fundamentals and connecting each concept to real-world projects is one of the best ways to grow.
This is just the beginning of my AWS journey, and I hope to share more of what I learn as I advance in my studies.
Thanks for reading!
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article