.svg)
Share
Copied!
DDSAM is an online education platform with the slogan “Easy to prepare for training, easy to operate.” When we share knowledge, our brain remembers images longer than text. Using sight and hearing not only reduces the burden on the brain, but also makes it easy to obtain information.
In order to reduce the education gap problem depending on the region, DDSAM thought of an online course and created it as a service. The process has been automated so that edits can be created quickly from shooting videos.
DDSam is a SaaS-based learning management system (LMS) construction service that allows anyone to develop a course website and LMS. CTO Kim Dae-hee on how to operate the service with WhaTap (hereafter Dae-hee) and developer Kim Ah-hyeon (hereafter A-hyeonI met) and listened to it myself.
Please introduce Santa and his duties.
A-hyeon: Santa is a development team composed of a total of 9 people, 1 CTO, 4 front team members, and 4 backend teams. Currently, all developers participate in development and operation in a DevOps manner, and backend developers manage the infrastructure.
How is Santa's IT infrastructure structured?
Dae-hee: The DiDi Tutor service is currently based on AWS. The backend API uses the AWS Elastic Beanstalk environment. In the case of databases, Amazon RDS and Redis are being used, and AWS resources are monitored by connecting to Watab. The front-end environment is configured by linking with AWS Amplify.
In the future, it is likely to move in the direction of multi-cloud, including the Naver Cloud platform. Our tech is operated based on relabel and PHP as a backend, and in areas that require performance, it runs in Java.
I'm curious about what led me to choose Watab.
A-hyeon: It was a time when DDSam needed detailed server load testing and API monitoring before the service was opened in September last year. CTO Dae-hee actively introduced Watap, and thanks to that, we even introduced it. The previous legacy service was using Amazon CloudWatch, but it was difficult to check detailed logs.
Dae-hee: I experienced the service development and operation process 3 times using Watab. After joining Santa in February of last year, I needed a tool to check and give feedback on the performance of the APIs being developed and the appropriateness of using the API on the front end due to the circumstances of the DiDi Tutor development process, and I gradually started using Watap monitoring from that point on. Currently, there are no major problems, and now all backend developers are making good use of Watab.
I'm wondering what monitoring tools you used before Watap.
Dae-hee: Previously, I used an installation-type application monitoring solution, and what I needed was developed and used in-house by collecting necessary indicators from within.
Did you make your own monitoring before the introduction of Watap?
Dae-hee: I developed it myself when monitoring was needed. In the case of monitoring, different perspectives are used from a development and operational perspective depending on the purpose.
Before the introduction of Watap, logging was performed to check various information such as service indicators and transactions and performance. When I introduced Watap, my emphasis was that “monitoring operates on behalf of developers.”
Without monitoring, development and resource input to operations are necessary. Monitoring reduces developer labor costs. I'm using Watab from that point of view, and I think it's comfortable and well done.
Can you tell me more about the labor cost savings perspective?
Dae-hee: If you don't use monitoring tools to develop your own services, internal developers will eventually have to use separate development resources for the parts needed for monitoring purposes. Monitoring-related modifications must continue to be made as needed during the operation process. Ultimately, it's a structure where developer resources must be used for additional parts other than the original service.
In that respect, I think that using monitoring services can reduce the scope of development work for developers. I think 0.5 M/M (Men per Month) can be reduced.
What is Men Per Month (M/M)? It is a method of calculating the cost of a software development project. It is a method of setting project expenses by calculating how much one person can do in a month. Source: Han Kyung Dictionary of Economic Terms
What are the advantages of using Watab?
A-hyeon: When deploying a server, WTAP enables intuitive monitoring by simply installing and running an agent through a script. In the case of monitoring that was previously used, separate settings were relatively complicated to receive notifications, but Wa Tap was very helpful because it was easy to set notifications for each status.
In the case of a heatmap, it is easy to understand the usage of servers in that area, and it is also possible to check it intuitively.
Dae-hee: WhaTap is intuitive. When you first look at the Watap dashboard, you can quickly see that “something went wrong somewhere.” Such parts are organized and used as dashboards as much as possible.
Monitoring starts at the development stage!
Dae-hee: At the time of opening the DiDi Tutor service, the person in charge of service planning said it was the first time it was opened without problems. The reason for the smooth opening of the service is that we have been preparing to open the service by using Watab step by step, from function tests at the beginning of development to performance tests. We've made up areas where there may be problems with each course.
1. Configure a dashboard on the Flex board to check API status and server status
2. Tracking and improving APIs that take a long time to respond or have errors
A-hyeon: In the early days of opening, it helped improve APIs and slow queries that take a long time to respond. It was also easy to anticipate and track user scenarios involving problematic APIs. Above all, we were able to quickly identify and improve issues through an intuitive UI and heatmaps.
Dae-hee: If you're a backend developer, of course you should use Watab. From a developer and engineer's point of view, this kind of experience is also important. They say “value for money” is good. I think it can be more effective than monitoring. If you don't develop monitoring yourself, I think CTOs and back-end engineers will fully sympathize with the need to adopt monitoring.
A-hyeon: If you are an early startup, want to quickly build a monitoring solution, and want to operate a stable service, I highly recommend Watap Monitoring. By installing an agent on the API server, you can monitor the server with an intuitive and easy-to-read UI.
Developers can also check the API where the problem occurred, and can more easily identify which process occurred, and help improve the service.
WTAP played a major role in being able to continue providing improved services to users at the same time as building the initial service. Thank you for your continued support 😊
