Today most web-apps are hosted on web servers like Apache etc. These web-servers are deployed virtual/physical servers in a data-centres. The only way you scale is via adding a load-balancer on top and having the right idle infrastructure which can be added as requests increase.
What changed with cloud?
Lets take example of AWS. AWS today provides global components like CDN, Lambda@Edge, S3 etc.
With CDN you can delivery the content to your customer from nearest data-centre of your cloud provider.
With Lambda@Edge you get 5 seconds of compute time at nearest data-centre of your cloud provider.
With S3 you get access to globally synced file storage system scaled in real-time.
The Serverless web-server
With these components available (content delivery, compute, storage) on cloud providers, imagine a web-server which
- enables automatic content delivery via CDN.
- identifies slow changing vs fast changing content and uses a global storage for faster response
- leverages the edge-compute to execute the business logic of the request.
With kitsune you can enable this in matter of minutes
- Import your existing application as an endpoint into a project
- Publish the project to the cloud provider of your choice!
kitsune would automatically create a serverless web server on the cloud and use your existing application as the origin. The runtime would first trigger a deep crawl to identify (and copy if required) slow changing vs fast changing content of your application. It then would leverage a global storage (like S3 on AWS, Blob Storage on Azure) to store the slow changing content and accelerate the responses.
kitsune would also expose APIs for you to trigger a fresh deployment or manage the environment.