Designing Scalable Systems

I applied and watched it all at once! This course is introduced as a course for beginners, but I think it's content that will be helpful to everyone in the IT industry! When you're running towards your goal of studying, getting a job, or changing jobs, you can easily get caught up in the 'trees' and not see the 'forest'. (That's what happened to me...😭^😭) Even before taking the course, I had heard of and knew concepts like 'search engine' and 'scale out'. However, I didn't systematically organize and understand why they were needed and how they developed after implementation. So if I had explained the content covered in this course, I would have ended up focusing on specific concepts (trees) that I knew the best. However, this course allows you to naturally understand how these concepts are connected and expanded into a huge service that handles traffic from all over the world!! Thanks to this, I was able to look at service design from a broader perspective! The course progresses in a way that makes it feel like one thing leads to another, so it was so fun that I watched it all at once, but I think I'll be checking it out often in the future!

I had the chance to hear this content in another lecture by the instructor, and I enjoyed it so much that I thought I had to listen to it again when it came out as a lecture. I always study the details, so I wanted to know the big picture, and this is a good lecture that helps me understand what part of the project I am involved in and how it is related to other parts. Having a perspective that looks at the whole picture from a distance makes me feel like my vision has become much wider.

The diagrams are well-organized and easy to understand!

I was able to improve my 'scalable web application design' skills by taking this course. I highly recommend it to students/job seekers who want to grow as web developers, especially backend developers! One of the most difficult things I faced when I started studying web development was 'knowing why certain technologies are needed'. In particular, I only knew about the structure of the web, such as servers, databases, and clients, but when I entered boot camp and carried out projects, I had many opportunities to encounter unfamiliar technologies such as Redis, Kafka, RabbitMQ, and Elasticsearch. I heard that it would be good to gain experience using these technologies, and I even tried some of them. However, I felt that these were not to solve a 'problem', but rather to leave them as just 'helpful experiences', which was a shame. Then, while listening to this lecture, I was able to resolve many of the things I was curious about. Starting with the most basic functions, the lecture presents problem situations, introduces the technologies that can solve them and how they solve the problems, and finally introduces representative examples of the technologies. As a result, the concept that 'B solution (technology) can be used for problem A' is established when designing a system. In addition, whenever a technology required for system design is added, it is shown as an architecture diagram, and the lecture is provided so that the flow and structure of requests/responses can be easily understood. Ultimately, I believe that you can effectively respond to problems that occur when creating web services, and also develop the technical ability to solve problems. Currently, I am taking the lecture and re-creating the structure of the project I made before based on the lecture content. I can see the parts that I did not understand before or the parts that I designed inefficiently, and I was able to create a more improved structure. I hope that other people who are studying web development will also develop the ability to design scalable and efficient web systems in future projects by taking this course!! :)

I enjoyed it so much. It feels like the fundamentals that I should always be seeing, hearing, and practicing, but I think I become lax because I'm always exposed to them. As a result, I find it difficult when problems arise in projects. This lecture simply shifted the perspective I was missing. It talks about stories that I encounter so often, but it feels new every time I hear them. Thank you for the great lecture.

It's good for a light and easy overview of system design basics. It seems helpful to refer to when you urgently need to recall basic content.

I was able to have a great study experience with neatly organized lecture materials in pictures and concise explanations that didn't miss the key points. I liked that each episode was short and not boring.

When I do projects or study on my own, I tend to get caught up in the technology. I somehow use it, but I have also caused a nuisance by slowing down the overall progress of team projects due to excessive learning that is not appropriate for my skills. So until recently, I have been trying to change my attitude of getting caught up in technology, but I still can't help but want to challenge myself with new technologies. So I was looking for a way to change this attitude. Then, I found a clue through this lecture. As I followed the problems presented in the lecture and the thought process to solve them, I began to think in a problem-solving-centered approach, such as "Why was this technology created?", "What problem did it appear to solve?", and "Is it a necessary technology?" rather than simply wanting to learn new technologies as I did before taking the lecture. Thanks to this, I was able to learn the thought process of exploring and applying appropriate technologies as needed rather than blindly delving into new technologies. I highly recommend this lecture to those who have similar concerns like me. Thank you for the great lecture!