Reverse proxy, load balancer and HTTPS front-end for Web server(s), implemented in Erlang. Why Erlang? My goal is distributed, rocksolid frontend, which can handle a lot of connections without putting big load on the hardware.
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.001590s ]
SELECT `a`.`aid`,`a`.`title`,`a`.`create_time`,`m`.`username` FROM `jrk_downrecords` `a` INNER JOIN `jrk_member` `m` ON `a`.`uid`=`m`.`id` WHERE `a`.`status` = 1 GROUP BY `a`.`aid` ORDER BY `a`.`create_time` DESC LIMIT 10 [ RunTime:0.124720s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.011058s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.001976s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.001461s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.005698s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.001847s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.007531s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.038571s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.001535s ]
UPDATE `jrk_articles` SET `hits` = 2 WHERE `id` = 287646 [ RunTime:0.012914s ]
