Origin Service

the nativewaves origin service allows you to create gateways via an api that can be integrated with traditional http based content distribution networks (cdn) the origin service's purpose is to act as "origin" in your existing infrastructure for all content stored at nativewaves this allows you to utilize your existing cdn provider and benefit from your existing data plans (normally in cost per gb), but still be able to load all necessary content from the nativewaves cloud platform the content flow is as follows graph td; a\[nw origin gateway] >b\[cdn provider]; b >c\[user application]; nativewaves only charges for the transferred gb and the number of requests between the origin and the cdn, but not to the user application therefore, you can optimize your costs and manage your scaling requirements independently of the content stored at nativewaves an origin gateway provides 100 gbit/s output per default please contact us if you want to increase this limit for your origin gateway the connection between the cdn and nw origin is secured via https and a security key the connection between the user application and the cdn provider can be secured by various cdn security mechanisms that may require custom development (e g token authentication) the origin will serve video and audio streams via e g http live streaming (hls) and handles all necessary cache control headers and compression the origin is deployed as a distributed service in the cloud and protected by various distributed caching layers for reference, a conventional 1080p video stream including the full bitrate ladder (720p, 540p, 360p, ) consumes about 20 mbit/s (depends on the codec, here we assume h 264) this equals 9 gb per hour so if you want to stream an event for 2 hours and expect an average of 10,000 users this would result in 180 tb of traffic between the cdn and the user application with a bandwidth requirement of 200 gbit/s the traffic between the origin and the cdn would only be about 18 gb with a bandwidth requirement of 20 mbit/s , if we assume perfect caching and no additional requests for expired content