Immediate ROI is accelerated web application.
ROI may defer from customer to customer.
Please refer case studies for more details.kitsune framework is built on top of serverless/cloud native framework.
Since the application isn’t hosted on any specific server, it never exposes any IP or any port (apart from 80/443) to the external users.
Since the data access is handled server side, and only plain HTML is the output, hence no one can access the business logic and database.
Riverbed Steelhead is majorly used within the WAN network. The performance and accelaration is limited to the the network latency within WAN network. It doesn't provide caching, compression or any customization at application level.
F5 - AAM: Is the competition with respect to Caching and compression. But it only provides caching at LoadBalancer level.
kit-proxy provides the caching at edge locations like CDN. F5 only caches at single location.
kit-proxy additionally provides edge compute to customize request and response
kit-proxy can provide:
- All the customization power of caching (multi tanent, header based etc..)
- Custom security(CSRF),
- Addition of custom functionalites like access control, dynamic ad insertion, A/B testing, image manipulation and more.
- Brotli Compression as standard.
Limelight and BitGravity: Are competition at some some level. Refer competition analysis for more details
Since Akamai CDN is providing all the values of CDN, kit-proxy can provide:
- All the customization power of caching (multi tanent, header based etc..)
- Custom security(CSRF),
- Addition of custom functionalites like access control, dynamic ad insertion, A/B testing, image manipulation and more.
- Brotli Compression as standard.
In case of dynamic request(insert data to db), kit-proxy will provide tunnel directly to the end application, there won't be any accelaration.
But since the request is passing via kit-proxy, it will be trasfered via dedicated private network of Cloud, hence the latency would be decresed(in miliseconds)
All the request / data will travel via kit-proxy middleware.
CDN will only check against the request path and parameters for the response to be served from Cache or Origin
kit-proxy customers can customize the logic to cache the content based on various parameters (i.e Headers, Browsers, Location, Cookies etc)
With respect to LoadBalancer, kit-proxy can be setup on top of LoadBalancer. Kit-proxy and LoadBalancer's purpose are different.
kit-proxy is used for performance improvement via caching and security via customizations where LoadBalancer's task is to distribute the request + standard security features
Riverbed Steelhead is majorly used within the WAN network. The performance and accelaration is limited to the the network latency within WAN network. It doesn't provide caching, compression or any customization at application level.
F5 - AAM: Is the competition with respect to Caching and compression. But it only provides caching at LoadBalancer level.
kit-proxy provides the caching at edge locations like CDN. F5 only caches at single location.
kit-proxy additionally provides edge compute to customize request and response