Completing a Full Cycle of Backend Service with Spring Boot and AWS

API: How clients and servers communicate, requesting and responding to data

API is a set of rules for communication between programs. Like a menu in a restaurant, it is a specification that determines what a client can request and how the server will respond. Through the analogy of a menu, you can easily understand the concept of API and learn how it is used in actual web services.

API development practice created directly with IntelliJ

It doesn't end with just hearing the concept of what an API is. You can use IntelliJ to create an API where clients and servers exchange data, and learn the core structure of web services needed for practical work.

Docker: Understanding the Core Structure of Container-Based Development

How does Docker work? A daemon process called dockerd manages images and containers, and we issue commands through docker client. Understand the core components of Docker, such as images, containers, and registries, and learn structurally what role each plays.

AWS EC2: Accessing the Cloud Server Directly

Cloud servers are no longer a stranger. Create an AWS EC2 instance, connect directly to the terminal, and learn the basics of server operation that are essential for practical work by handling the Linux environment. Experience installing Docker, opening ports, and setting up security groups with your own hands.

Layered architecture, DTO, Entity separation: Reliable design through separation of responsibilities

How is the backend application structured? Layered architecture separates the application by role to improve maintainability and scalability. Each layer of controllers, services, and repositories has a clear responsibility, and DTO is an object for passing data between layers and should be separated from Entity. Learn structurally why this separation is important and how to design it.

Database Index: Understanding the Internal Structure for Fast Searches

How does a database find data quickly? An index is used to speed up the search for a specific column in a table, and acts like a table of contents in a book. Understand the internal structure such as B-Tree and learn structurally in which situations an index should be used to improve performance.

Pagination vs. Infinite Scroll: Efficient Data Delivery Beyond the Limitations of OFFSET

OFFSET -based queries, which are commonly used when displaying a large amount of data in a divided manner, show a sharp decline in performance as the page goes back. This is because the DB scans the data corresponding to the OFFSET before returning the desired results. In the backend, improvements are made to resolve this issue through methods such as cursor-based pagination or ID-based range lookups . We will structurally examine pagination and infinite scrolling, as well as the differences in UX and changes in query strategies for performance optimization.

Post and comment correlation and transaction processing

In JPA, when establishing relationships between entities (such as Post-Comment), you can automatically reflect changes to the database at the time of transaction commit through change detection (dirty checking). You will also learn how to utilize change detection within a transaction, how far to group work units, and strategies for stable data processing along with relationship settings.

How to Use Git: Beyond Simple Commands to Strategies for Collaboration and Stability

Git is the most widely used version control tool by developers, but it goes beyond simply storing code and plays a key role in collaboration and quality control. When working alone, basic commands such as commit , push , and pull seem sufficient, but team development requires a more structured approach such as branch strategy and commit history management.

In actual work, Git is used to organize the code review flow, ensure deployment stability, and provide a foundation for team members to perform work in parallel. If Git is used properly, it can reduce confusion that may arise during the collaboration process and increase development productivity.

We will cover not only basic usage, but also branch strategies and workflows frequently used in practice.

GitHub Actions and AWS SSM Integration: Secure and Convenient Authentication via OIDC

One of the concerns when accessing cloud resources in the CI/CD pipeline is the authentication method. Previously, it was common to register AWS IAM user keys in GitHub Secrets and use them, but this came with the burden of periodic key replacement and exposure risk.

You can securely access AWS resources without an IAM user key by utilizing OIDC (OpenID Connect) supported by GitHub Actions. AWS verifies the token issued by GitHub and grants temporary permissions, so you can have both security and convenience without separate key management.

We will look at the GitHub Actions and AWS OIDC integration structure and learn about specific setup methods and how to apply them in practice.