Kotlin Master Class: Learning Through Bank Server Project Practice

Learning Kotlin through Bank Server Project Practice

Are you ready to go beyond simply learning Kotlin syntax and gain practical experience by writing a sample project for a banking server?

In this course, you will learn how to write efficient code with Kotlin's concise and expressive syntax, discover Kotlin's own solution that overcomes Spring's AOP limitations , and learn scalable log processing methods . You will also implement a scalable server yourself using Redis, Kafka, MySQL, and MongoDB , and apply methods for solving concurrency issues in practice.

The problems that occur in the financial domain are diverse and complex. We cannot cover everything in one lecture, but we provide an opportunity to solve real problems that people who wish to enter the financial domain or learn Kotlin in depth.

Don't just end with theory, but make technology that can be applied directly to actual services your own. It will be a time to think together and grow.

Why should I learn Kotlin..?

It is said to be 100% compatible with Spring, and Kotlin, a language created by Jetbrain, is optimized for concurrent programming, which Spring is not suitable for.

After taking the lecture, you can create results like this.

Technology stack covered in the lecture

4 Core Values We Hold Dear

Course Structure

⏩Section 2

This briefly covers model management that I dealt with while experiencing practical work.

This includes my personal perspective on what would be the best approach to handling types, based on Google's design patterns.

⏩Section 3

We will proceed with code work to implement scalable code for OAuth2.

OAuth2 is a feature that can be continuously added depending on platform characteristics. We'll show you how to implement scalable code through interface handling for this functionality.

⏩Section 4

In this section, you will learn about how to overcome the limitations of AOP in Spring using Kotlin.

Spring AOP is a concept that is widely applied and used without you realizing it. It is used to ensure data persistence for conventional databases, and is also utilized in logging processing using PointCut.

However, it's a disappointing friend that has several drawbacks. This section covers how to use Spring's AOP more flexibly in Kotlin.

⏩Section 5

You will work on an API that has completed the implementation of OAuth2 functionality and even applied AOP.

Through this process, you will implement and write code for the first time together with me, verify that it works correctly, and also have time for debugging through this process.

⏩Section 6

Further code development will proceed for features that are more suitable for B2C and B2B applications.

You will implement together how to execute specific Service Logic based on incoming traffic and how to implement functionality.

You will write business logic together using @Service, @RestController and others.

⏩Section 7

Redis is a very important element in practical work. It can be used to control concurrency and is used for CPU optimization of databases through cache processing of data.

In this section, you will work with various methods that can utilize Redis and Redisson.

⏩Section 8

Now you will begin writing the logic for concurrency control in earnest, utilizing the Redis-related methods that were written earlier.

We will work together to write a Distributed Lock for sequential processing of simultaneous incoming traffic, and it will be a time to write logic together to ensure data persistence.

⏩Section 9, 10

In this session, you will implement code directly using Kafka. You will utilize Kafka's Producer to handle event changes occurring in the API, and use it as code that leverages loose coupling between services and polyglot persistence strategies.

You will implement code for MongoDB and develop the corresponding service logic. Additionally, you will implement and work with logic that reduces database usage through memory utilization.

⏩Section 11

Spring Security is responsible for handling the logic that processes incoming API requests in advance.

This process has the disadvantage of increasing the number of points that need to be managed, but we will implement it together with the advantage of being able to optimize additional resources accordingly.

⏩Section 12, 13

You will create a new module to handle Kafka's Producer and implement logic that communicates with MongoDB and Redis, thereby covering the process of generating data suitable for different traffic types. Through this session, you will learn what loose coupling is and what message processing methods are.

Important Notes Before Taking the Course

A great lecture to watch together!