[Reservation Program] Extra. Current hosting using cloud computing and selection of domestic hosting company

Why did you change to a domestic hosting company?

We decided that there was a possibility that server costs would be higher than expected when using AWS, so we decided to use a domestic hosting company to reduce uncertainty. Therefore, on the client side, the traffic or database usage scale has not yet been clearly determined, so the burden of high costs is high.

• This article is not an advertisement.

---

Estimated cost of a website developed based on the existing AWS EC2 and RDS free tier

This is last month's AWS bill. Currently, we are using 3 EC2 and 2 RDS.

When calculating only the costs related to this project on a monthly basis,

• EC2 costs $17.05
• ELB costs $1.15
• Ragistrar cost (domain purchase) is $12.00 (once per year), so $1.00 per month.
• RDS costs $2.79

So, on a total monthly basis, this project cost $22.99.

However, this price is available when using AWS's free tier service for the first year, but when considering long-term website operation, the cost is quite different.

When using an on-demand instance (EC2), the on-demand hourly rate is 0.0144 USD in the same region and instance specifications (t2.micro) as the current free tier. In other words, the EC2 fee alone costs approximately $10.368 per month (based on 30 days). If the other database costs applied above are included here, the monthly fee does not meet the client's requirements.

Of course, we also considered the smaller Lightsail plan, but with monthly usage of $3.50 + monthly single fee of $18.00 for load balancer + database fee of $15.00, even considering only the standard plan, it costs about $36.50 or more. Considering taxes and various other costs, it is expected to cost around 50,000 won, which means that moving to a small hard drive within AWS did not have much merit when comparing prices with domestic hosting companies.

---

First, the server selection criteria are as follows.

1. The server was selected as a relatively safe server located in Korea.
2. A product with adequate traffic based on 150 daily users and a relatively large DB volume
3. A place where the monthly cost is about 50,000 won or less and the cost burden of website redistribution is low.
4. The development language must be a supported specification

We selected and compared suitable products from the top 3 domestic hosting companies: Cafe24, Blue Web, and Gabia. Because the price was relatively lower than AWS, it was inevitable that the hard drive and traffic capacity would be small. I know that most hosting websites do not support downgrades, so I plan to purchase a product with a small capacity first and upgrade later. And although there are many inexpensive hosting companies overseas for domestic applications, we chose a domestic hosting company for speed and convenience of response.

Compare hosting products

Company name	Product name	monthly fee	hard (web)	traffic	DB	domain	mail	installation fee
Cafe 24	Tomcat JSP Business	5,500	2GB (1GB)	4.5GB	unlimited text	5	30	11,000
Gabia	JAVA basic	9,500	2GB (1GB)	30GB	borderless	-	5	10,000

The current project specification is an application implemented using thymeleaf in HTML without using JSP, and the language is based on Java and JS. (As those who use IntelliJ will know, we are gradually moving away from JSP. It has become much simpler than when we first implemented applications with JSP in Eclipse. I also saw an article saying that JSP is better in terms of performance.)

Cafe24's MariaDB specifications were supporting 10.1x, which is lower than the current 10.5x version of the application.

Gabia only supported Java through container hosting, so the price was somewhat higher than Cafe24. Of course, it's container hosting...

Blue Web did not have a favorite product suitable for the current project.

(I was interested because there were many Java-based web hosting services overseas, but considering the speed and response, I couldn't abandon domestic hosting.)

First of all, I decided to choose Cafe24's Tomcat JSP business. I liked the fact that it was the same as MariaDB and the Java version was also the same. And above all, I thought that 4.5G would be enough because the cost was low and the traffic was not likely to be large for the number of participants. (트래픽 계산 참고)