Tigris object caching demo with Elixir and Livebook

hi my name is zugo and this is a demo of Tigress object caching with liter and lightbook so what we are going to do here is we use TIG API first to upload an object to a TIG bucket and then we are going to use those machines that are set up in different cities around the world to download that file but has four machines one in Mobile One in Boston one in s Paulo and one too and you want to see the latencies to download that fire on those different settings okay so this notebook is also a live book app and let's first launch this app we're going to laun the app locally want to review the app locally let's open the app and let's upload a file to S bucket going to select the scat file here once the f is uploaded you can see it here and I also buil this simulator so we can see I'll making request from different cities to typ book it works so let's say that first request are going to make it's from s Pao that's where I am and that's from the file was uploaded so the blue marker is the request location and the gray marker is the response location we can see that the request was made from s Paulo and the response also came from Tigers region s Paulo and it took three Mills what happened here is that when I upload a object to a TIG bucket Tigress will automatically start that object in the closest region to the uploader since the uploader in s Paulo the closest region is in so Pao so that's where it was stored let's try making a request from different city so if make a request the same URL from Mumbai you can see they would take a little bit more time that was because of the latency lat latency between those two cities the request came from Mumbai the response came from so Paulo and it took 2.7 seconds but if I request the same object again a second time we can see that the response coming from a different place s is coming from s Paulo now the respon is coming from Singapore what happened here is that whenever someone makes request to a object stor in a tigress bucket Tigress will automatically cash that file in the closest region from the person making the request so the person making the request in Mumbai and the closest region is in Singapore to from the second and third and someone Quest the latest should be way better compared to the first one so can continue to make some more requests you can see that the latency is way better and this happens for other cities as well so I make request from Boston going to take some time the requests will come from some follow and the response is going to be like 269 milliseconds but when I make a second request the response going to come from Washington DC which is closer to Boston compared to some poers and the last city is going to be Tokyo let's make a from Tokyo response going to be from s Paulo because that's where the object was originally stored and we can see that the latency was little more than two seconds and if I make a second request the lat is 4 milliseconds let make another 3 milliseconds we see SE here I buil this table view as well besides the map F can see a summary the history of requests so for example for Mumbai for the first request the response came from s Paulo and and it took 2.7 seconds but the second and third request the response gonna come from s of for with schoser and that happen well for Boston first response from so Paulo second response from Washington DC way better latency as and the same happens for Tokyo or any other city and I think that's awesome because will help you to have great latency for your users and also great the act because I don't have to specifically say where I want to store those files we store closest to the uploader and then we cash the file closest to the users that's it