What exactly does "based on HAProxy" mean? Built with the same purpose of HAProxy in mind, is it a fork? Curious to how you decided to improve upon it. Looks impressive, might have to give it a try myself.
nuster uses the source code from HAProxy and added cache functionality on top of it. nuster is not built with the same purpose of HAProxy, but with the powerful features of HAProxy, like load balacing/ACL.
nuster started from HAProxy v1.7 when there was no small cache ability in haproxy, which was introduced in haproxy v1.8.
But the cache introduced in haproxy1.8 has many limitations, for example only small response can be cached, which defaults to 16KB as defined by the global parameter tune.bufsize, while nuster can cache any size response.
Also haproxy1.8 cache only works for 200 and GET, while nuster can cache any http code and POST/PUT.
Also haproxy1.8 cache can only use host and urias key, while nuster can use header, cookie, query as key too.
And nuster has PURGE functionalities, disable/enable at runtime functionalities, stats, and so on.
Please do give it a try, any feedback is welcomed:)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What exactly does "based on HAProxy" mean? Built with the same purpose of HAProxy in mind, is it a fork? Curious to how you decided to improve upon it. Looks impressive, might have to give it a try myself.
nuster uses the source code from HAProxy and added cache functionality on top of it. nuster is not built with the same purpose of HAProxy, but with the powerful features of HAProxy, like load balacing/ACL.
nuster started from HAProxy v1.7 when there was no small cache ability in haproxy, which was introduced in haproxy v1.8.
But the cache introduced in haproxy1.8 has many limitations, for example only small response can be cached, which defaults to 16KB as defined by the global parameter tune.bufsize, while nuster can cache any size response.
Also haproxy1.8 cache only works for 200 and GET, while nuster can cache any http code and POST/PUT.
Also haproxy1.8 cache can only use host and urias key, while nuster can use header, cookie, query as key too.
And nuster has PURGE functionalities, disable/enable at runtime functionalities, stats, and so on.
Please do give it a try, any feedback is welcomed:)