<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Greta.io - Medium]]></title>
        <description><![CDATA[Understand, manage and improve your delivery performance. Greta chooses the best delivery method for every piece of content, using machine learning to analyse network data in real-time. - Medium]]></description>
        <link>https://medium.com/greta-io?source=rss----3e1bf5de3afb---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Greta.io - Medium</title>
            <link>https://medium.com/greta-io?source=rss----3e1bf5de3afb---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:01:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/greta-io" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Greta is no more. Here’s why.]]></title>
            <link>https://medium.com/greta-io/greta-is-no-more-heres-why-6f4f87cb3842?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f4f87cb3842</guid>
            <dc:creator><![CDATA[Anna Ottosson]]></dc:creator>
            <pubDate>Thu, 05 Apr 2018 14:22:02 GMT</pubDate>
            <atom:updated>2018-04-05T14:42:49.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NuHuupFaaxexvUgh5e5-NA.jpeg" /></figure><p><strong>A few months ago me and my two co-founders Dennis and Victor came to the decision to stop building Greta.</strong></p><p>The irony is that if we had been able to get a preview of the 6 months leading up to this decision back when we started out, we would probably have jumped with pride and excitement. Things were finally falling into place, and it felt like the world was moving our way; we onboarded more and bigger users, we had interest from some of the worlds’ largest media and retail companies, we joined the amazing Heavybit community. We were offered additional financing by amazing investors, and we had built a fantastic team that made it a true joy to work. The product got praise, we were listed as one of the hottest startups by Wired, we got on the radar of some of the world’s most accomplished minds in the infrastructure space who offered to help in different ways, and we were making progress in a higher pace than ever. After two years of what felt like pushing a heavy snowball up a mountain; we were finally over the edge and things felt easy (well, easier…).</p><p>One thing that I have learned about having cofounders is that you over time develop an almost joint sense of intuition. Before you have all data, before you have articulated arguments, before you have said things out loud; there is this ungraspable notion of something deep down — and at least for me, Dennis and Victor we’ve more often than not become aware of that notion’s existence at roughly the same time.</p><p>This was no exception, and one sunny San Francisco afternoon we dared to articulate it; deep down something didn’t feel right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blJsubzmy1NqnaoWV5Sv8w.png" /></figure><p>When we started Greta we promised each other one critical thing; to never build a company just for the sake of building a company. The purpose of Greta was to make a positive impact for Internet users globally, and if we one day felt that we wouldn’t be able to have the degree of impact that we wanted, we’d prefer to quit. The thought that we now dared to articulate was; “is this that day?”.</p><p>When we started Greta we had three fundamental hypothesis around the continued development of Internet infrastructure;</p><ol><li>There would be a focus shift from hardware to software as ML/AI technology significantly improves the ability to use available network and client data intelligently to optimize performance.</li><li>There would be endless opportunities in fast growing countries like India where the demand for content consumption would require fundamentally new ways of delivering Internet content.</li><li>Companies with heavy content would opt for 3rd party options rather than building in-house solutions, and favour easy-to-use developer platforms that left them in control.</li></ol><p>At this sunny afternoon, we concluded that all of these hypothesis had proven true. However, this also meant that the playfield now looked significantly different than when we started. Amazon is investing massively in its cloud and infrastructure businesses, Google is rolling out impressive projects like Google Station and Youtube Go in India as part of its Next Billion Users initiatives, and keep on developing infrastructure projects like <a href="https://www.blog.google/topics/google-cloud/making-google-cloud-faster-more-available-and-cost-effective-extending-sdn-public-internet-espresso/">Espresso</a>. Impressive companies like Fastly and Cloudflare are challenging how developers think about content delivery and edge cloud capacity. In this new playfield, we no longer truly believed that Greta would have the ability to be the company pushing the boundaries of Internet performance. Could it become a financially successful company? Without a doubt. Was it still in line with the promise we made to each other when we started it? No.</p><p>The discussions that followed with the rest of the team, investors, advisors and other people that had helped us along the way obviously weren’t easy, but everyone agreed that if we no longer felt that we could truly have the big impact that we wanted, letting go was the right thing to do. We’ve been extremely fortunate to surround Greta with incredibly intelligent, kind and respectful people, and I’m truly overwhelmed by the support we’ve received.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8T6Z6RG7wyUglHEHSTqo2Q.png" /></figure><p>Since the decision to stop working on Greta we’ve all taken some much needed time to reflect on our own individual goals and dreams, and we’re all incredibly excited about what’s next. For some of us; myself, my cofounder Dennis and our first hire Pierre-Louis, the decision has landed on joining the amazing team at Fastly. Since we started Greta we’ve not only been impressed by their ability to build high-performing technology, but also the incredible people we’ve met there; people with high integrity, tons of knowledge and a good portion of humor.</p><p>Their journey so far is breathtakingly impressive; they’re one of the top 10 fastest growing B2B tech companies of the last 30 years with customers like The New York Times, AirBnB, Spotify, The Guardian, Firebase, Etsy, Twitter, Github and many more, and today serves over 10% of all Internet requests. We’re super excited to join their team, and look forward to keep working towards the purpose we had from day 1; improving Internet experiences for users globally.</p><p>The last years have been extremely rewarding; and me, Dennis and Victor are incredibly proud of what we’ve accomplished. The strongest feeling of them all is how grateful we are for all the amazing people we’ve been fortunate enough to get to know, and we’re of course especially grateful towards those who decided to join Greta’s mission in different ways — you are the best!</p><p>The amazing amazing Greta team, our users, the brilliant Jason Whitmire at BlueYard and our other investors Hampus Jakobsson, Sophia Bendz, Jan Erik Solem, Jeremy Yap, Erik Byrenius, Anna Nordell, Stefan Lindeberg, Anders Frankel, Marcus Wallén, Alfred Ruth, Tommy Andersen and Tim Jackson, the entire Heavybit team and community, as well as people like Serge LaChapelle, Niklas Zennström, Chad Fowler, Ameet Patel, Jonathan Heiliger, David Roldan, Gus Maskowitz, Daniel Bergqvist and many many more who’ve generously shared their time, input and help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f4f87cb3842" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/greta-is-no-more-heres-why-6f4f87cb3842">Greta is no more. Here’s why.</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Releasing Greta Lighthouse — site performance report based on real user conditions]]></title>
            <link>https://medium.com/greta-io/releasing-greta-lighthouse-site-performance-report-based-on-real-user-conditions-8295b54187c7?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/8295b54187c7</guid>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Dennis Mårtensson]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 14:57:35 GMT</pubDate>
            <atom:updated>2017-12-01T14:57:35.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zsxo_rUqYbPzrzG51DXuxw.png" /><figcaption>Greta Lighthouse — check your site performance insights based on real user conditions</figcaption></figure><p>Performance is one of the four focus areas for Google Lighthouse, which is what we have based our tool upon. We just released a new tool to generate a report providing deeper &amp; more accurate insights into your users’ perceived performance. Considering parameters such as geography and type of device to simulate real user conditions.</p><p>Try it out here: <a href="https://lighthouse.greta.io/">https://lighthouse.greta.io/</a></p><p>We think this is valuable and hope you’ll find it too! <br>We’re happy to get feedback or answer any questions you might have.</p><p>It’s available for free as of today!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsTPoqtdqB0eEUH5RdfGGw.png" /><figcaption>Example of the performance report</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y9YgG7m5bkV4iw9VyYGvXg.png" /></figure><p><strong>What is Lighthouse?</strong></p><p><a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a> is an <a href="https://github.com/GoogleChrome/lighthouse">open-source</a>, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, and more.</p><p>Greta.io is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff7eaea%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Ff7eaea%2F&amp;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff7eaea%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/26a6bbc4d4169f4046c6f2ae51d167a5/href">https://medium.com/media/26a6bbc4d4169f4046c6f2ae51d167a5/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8295b54187c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/releasing-greta-lighthouse-site-performance-report-based-on-real-user-conditions-8295b54187c7">Releasing Greta Lighthouse — site performance report based on real user conditions</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated time-to-interactive measurement]]></title>
            <link>https://medium.com/greta-io/automated-time-to-interactive-measurement-cfd6d16e3b59?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/cfd6d16e3b59</guid>
            <category><![CDATA[it-infrastructure]]></category>
            <category><![CDATA[chrome-extension]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Pierre Dubouilh]]></dc:creator>
            <pubDate>Mon, 25 Sep 2017 13:38:20 GMT</pubDate>
            <atom:updated>2017-10-02T21:44:49.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6KOczi9h_BEyadSoRP2Mg.png" /></figure><p>After watching last week’s talk by <a href="https://twitter.com/benschwarz"><strong>Ben Schwarz</strong></a> at <a href="https://www.youtube.com/watch?v=p5ctfOdAAM8">NordicJS</a> (<a href="https://speakerdeck.com/benschwarz/beyond-the-bubble-1">slides</a>) on real-life web performance, we decided to release a small script we used internally; here comes <a href="https://github.com/gretaio/tti-observer"><strong><em>tti-measure</em></strong></a>.</p><p>At <a href="https://greta.io/">Greta</a> we constantly seek for better web-performance, and measuring a realistic figure regarding end-user web-page performance is crucial for us.</p><p>It used to be somewhat difficult, with lots of different metrics available (DOMContentLoaded, onLoad). And that’s where <a href="https://developers.google.com/web/updates/2017/06/user-centric-performance-metrics">time-to-interactive</a> comes to save the game, as it provides a really realistic metric on websites performance. The tti is measured when the page is ready, usable, and when there were no long JS tasks for the past 5 seconds (cf. <a href="https://calibreapp.com/docs/metrics/time-to-interactive">calibre docs </a>for more explanation).</p><p>It still relies on new web API, so it’s only really usable on Chrome at the moment, with the help of a <a href="https://github.com/GoogleChrome/tti-polyfill">polyfill</a>.</p><p><em>tti-measure</em> consists of a simple tool, that runs the website you provide on chrome, injects the JS necessary to measure the tti, and measure the metric. It runs the site multiple times, and through different network profiles (3g, dsl), so you can be assured your website is realistically fast, even on bumpier connections.</p><p>Because we can’t live without CI, it’s very easy to implement it on a CI platform, just have a look at the <a href="https://github.com/gretaio/tti-observer/blob/master/.travis.yml">travis file</a> in the repo. It runs on sane default settings (different network profiles, <em>exit 1</em> if the tti is over 5 seconds), but it’s fully customizable for your needs/market.</p><p>Have a look, the code is on our <a href="https://github.com/gretaio/tti-observer">github repo</a>, and the install is just one command away: npm i -g tti-measure</p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance with an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfd6d16e3b59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/automated-time-to-interactive-measurement-cfd6d16e3b59">Automated time-to-interactive measurement</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WebRTC in Safari]]></title>
            <link>https://medium.com/greta-io/webrtc-in-safari-10f22aa0a567?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/10f22aa0a567</guid>
            <category><![CDATA[webrtc]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[safari]]></category>
            <category><![CDATA[peer-to-peer]]></category>
            <dc:creator><![CDATA[Dennis Mårtensson]]></dc:creator>
            <pubDate>Tue, 11 Jul 2017 14:01:44 GMT</pubDate>
            <atom:updated>2017-09-13T13:12:57.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OzPwQ5xe9D0mgAXKWwxtqw.png" /></figure><p>Since we started <a href="https://greta.io/">Greta.io</a>, one of the questions we have been getting regularly, is what browsers support WebRTC? We’re happy to finally be able to include Safari on that list. This is especially positive for the European and US markets which are iOS heavy regions compared to the rest of the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4q6J4KM50-gk1lqqnCWQ3A.png" /></figure><p>As Apple have announced, WebRTC will now make it’s way into Safari and iOS 11. In fact, if you are a registered developer with Apple you can already try out the beta version of Safari with WebRTC support.</p><p>Of course we’ve been working on making sure that Greta works in Safari and is ready as soon as the WebRTC support comes out, and we wanted to share a few things we’ve noticed when testing WebRTC in Safari so far:</p><p>For us, it has so far proven relatively easy getting Safari, Chrome and Firefox connecting to each other. One thing that we did however run into is that setting the session description protocol on the offer or the answer will throw the following error:</p><pre>TypeError: Attempted to assign to readonly property.</pre><ul><li>Using the WebRTC stats API is also a bit different compared to for example Chrome. If used without a selector in Chrome you get a number of stats, but doing the same in Safari will throw the following error:</li></ul><pre>Argument 1 (‘selector’) to RTCPeerConnection.getStats must be an instance of MediaStreamTrack</pre><ul><li>In other browsers, we create multiple Datachannels on the same Peer Connection, which does not seem to be supported in Safari. It might be that Apple is planning to add it later on, but either way it is something that we are able to work around. We would however preferred it if Safari worked in the same way as the other browsers as that enables faster data delivery.</li></ul><p>This is just a short note on what we have been seeing so far. If anyone else have tried it too and would like to discuss it more, feel free to reach out directly to me at dennis@greta.io.</p><p><strong>We are generally very happy with Safari and WebRTC, and believe it is a great step forward for WebRTC in general that the last big player joins the ecosystem.</strong></p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10f22aa0a567" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/webrtc-in-safari-10f22aa0a567">WebRTC in Safari</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real time data processing using Google Cloud and OpenTSDB]]></title>
            <link>https://medium.com/greta-io/realtime-data-processing-using-google-cloud-and-opentsdb-c87a45ea3cc2?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/c87a45ea3cc2</guid>
            <category><![CDATA[bigquery]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[google-cloud-dataflow]]></category>
            <category><![CDATA[apache-beam]]></category>
            <category><![CDATA[big-table]]></category>
            <dc:creator><![CDATA[Dennis Mårtensson]]></dc:creator>
            <pubDate>Tue, 11 Jul 2017 09:00:14 GMT</pubDate>
            <atom:updated>2017-09-13T13:13:27.222Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the first of a number of posts on how Greta.io performs high scale realtime streaming data processing. We will outline the architecture of the system and write a short summary of the different parts.</p><p>If you have read any of the previous posts by us, you will know that we are running on the Google Cloud Platform and that we have been very successful with using different offerings from Google to be able to run Greta.io at high scale.</p><p>First, some of parts of this were inspired by <a href="https://blog.serverdensity.com/time-series-data-opentsdb-bigtable/">Server density’s setup</a>. You will see that our system is not the same but has a few parts in common.</p><p>Before we start, we would like to thank Daniel Bergqvist from Google for helping out and sharing insights with us! 🙌🏽</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YckeCNFk6UJ8BKqPBhitbg.png" /></figure><p><strong>Client: </strong>The system we are building is collecting data from all the users of sites that are using Greta, building up a large number of data flowing into our system.</p><p><strong>HTTP(S) Load Balancing: </strong>The users of Greta are literally distributed all around the world, which requires global presence. We achieve this by using the globally distributed http load balancer from Google. This gives us very quick and reliable data ingestion from clients all over the world.</p><p><strong>Container Engine: </strong>We run all our services in <a href="https://kubernetes.io/">Kubernetes</a> with the help from Container Engine.</p><p><strong>Ingestion: </strong>We currently have 4 clusters, EU west, US west, US east and Asia east, where we are ingesting data. We constantly evaluate where to add new presence. This is where we consume http-requests and execute some data enhancements before publishing to the queue.</p><p><strong>Cloud Pub/Sub:</strong> Is used to move and distribute data. This service is hosted and runned by Google. To us the most important part is that it’s globally deployed so we can use it to move data from all the ingestion points around the world back to EU for streaming data processing.</p><p><strong>Apache Beam/Cloud Dataflow: </strong>Allows for realtime and scalable data processing. We use beam’s functionality for windowing, grouping and a number functionalities which requires global presence. We achieve this by using the globally distributed http load balancer from Google. This gives us the possibility of collecting a number of different output values, fast and easy add new values and new computations on the stream of data.</p><p><strong>BigQuery:</strong> We write all the data that flows on to Dataflow in to BigQuery which allows us to perform analytics and query the data at scale. We use BigQuery extensively to extract data and optimize data delivery for our customers, and give them insights to very specific parts of their data delivery network.</p><p><strong>OpenTSDB: </strong>Is a time series database that has a number of functions built in, allowing us to query data very effectively. We can very rapidly iterate on queries and use the multiple aggregations, downsampling, expressions, tags and more to visualize the data, giving insights in how the data distribution is preforming.</p><p><strong>Cloud Pub/Sub to OpenTSDB writer: </strong>This is a small static writer that subscribes to Cloud Pub/Sub and sends a write operation to openTSDB. The biggest benefit of doing it this, is that it’s enabled us to continue writing to the different data sources and to recover the data as long as it is remains in cloud pub/sub.</p><p><strong>BigTable: </strong>We run openTSDB with BigTable as the storage backend, which allows for basically linearly scaling in writes and reads. It is also completely managed and performing operations really quickly.</p><p><strong>Read API:</strong> We run an API that does authenticate the users and allows our front end to query openTSDB for data, that will then be displayed in our dashboard.</p><p>All in all, it’s a lot of parts but it makes the data processing very scalable and resilient. We will go in to the different parts of the system in different blog posts, to eventually provide a good in-depth overview of the system.</p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c87a45ea3cc2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/realtime-data-processing-using-google-cloud-and-opentsdb-c87a45ea3cc2">Real time data processing using Google Cloud and OpenTSDB</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our next step towards a fast and sustainable Internet for everyone]]></title>
            <link>https://medium.com/greta-io/our-next-step-towards-a-fast-and-sustainable-internet-for-everyone-b05e30102e62?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/b05e30102e62</guid>
            <category><![CDATA[peer-to-peer]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[p2p]]></category>
            <category><![CDATA[web-performance]]></category>
            <dc:creator><![CDATA[Dennis Mårtensson]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 14:17:36 GMT</pubDate>
            <atom:updated>2017-09-13T13:14:00.924Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B9X8NfQerwtO0OKmttM3GQ.png" /></figure><p>As the CTO of Greta.io I’m constantly thinking about the future of the Internet infrastructure and here I thought I’ll share some of the things that really excites us.</p><p>Every day we’re helping companies to distribute their content in a way that delivers the best possible end user experience.</p><blockquote>Today we’re doing this by adding intelligence and flexibility to your content distribution, and by extending your network with our dynamic cache solutions and our machine learning powered P2P distribution network.</blockquote><p>We’re using WebRTC to set up peer-to-peer connections directly between concurrent users of a site, and can thereby calculate the most efficient route for any piece of content. The benefits include faster load times, higher content quality and reduces cost, especially during traffic spikes.</p><p>What we’re doing today is only a first step of our plan to revolutionize the way content is distributed over the Internet, and to provide people with amazing Internet experience anywhere on the planet.</p><p>For every new deployment we do with Greta we get access to global network information, and can see how the network is behaving and performing in real-time. This network data enables us to optimize our routing algorithms and detect patterns and anomalies.</p><p>As we get access to more real-time network data we’re becoming better and better at customize and optimize the connection settings for parameters such as device types, network, time patterns and geographical position.</p><h3>So what’s next?</h3><p>A fascinating but at the same time natural next step in order to make the connections more reliable and well-performing is using the best cloud providers out there to introduce entry points to our network. But what really excites us is taking that approach even one step further.</p><p>By using technology very similar to what we’re today using for our P2P network we could create an intelligent <em>Overlay Network</em> by connecting all these cloud providers together and thereby route the data in the most optimal way from end to end. That would allow faster downloads and uploads with higher reliability, and is a great step in improving the Internet experience for everyone everywhere.</p><p>One of the keys to improving the Internet will be utilizing network knowledge in an intelligent way. Our ambition is to combine the following:</p><ol><li>The ability to make well-informed decisions in every end user device, such as phones, laptops, TVs and IoT devices.</li><li>The benefits or pushing content to the edge of the network.</li><li>Making optimal connections based on for example device type, network and geographical position.</li></ol><p>By doing so we will provide Internet users globally the experience they deserve, no matter their device or network connection.</p><p><em>Stay tuned for more, and email </em><a href="/service/mailto:projects@greta.io"><em>projects@greta.io</em></a><em> to get in touch.</em></p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b05e30102e62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/our-next-step-towards-a-fast-and-sustainable-internet-for-everyone-b05e30102e62">Our next step towards a fast and sustainable Internet for everyone</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Internet is scaling faster than today’s infrastructure can keep up]]></title>
            <link>https://medium.com/greta-io/internet-is-scaling-faster-than-todays-infrastructure-can-keep-up-e8719e7cc53d?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/e8719e7cc53d</guid>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[peer-to-peer]]></category>
            <category><![CDATA[p2p]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Anna Ottosson]]></dc:creator>
            <pubDate>Mon, 08 May 2017 11:06:02 GMT</pubDate>
            <atom:updated>2017-09-13T13:18:52.083Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Internet is scaling faster than current infrastructure can keep up. Here is why we care and what we’re going to do about it.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q98zBOOClGYh9gxKjhDRmA.png" /></figure><p><a href="https://greta.io/">Greta.io</a> is a Swedish company, and our vision is to upgrade the Internet for everyone, everywhere. This is how we see the future of the Internet and how we can improve that future.</p><p><strong>Right now, one thing is abundantly clear. Over the past 25 years, the Internet has evolved by leaps and bounds. It started as a small network of connected university servers where researchers shared text documents, and it transformed into one of the most critical building blocks of modern democratic societies.</strong></p><p>For example, access to the Internet accelerates the formation of new ideas. <br>It boosts economic growth. It provides useful knowledge and information to people around the world every single day. It enables you to meet people who would be otherwise impossible to find. It allows journalists to spread important facts. And it democratizes culture and education, taking them out of the hands of a privileged few.</p><p>Now here’s the technical challenge that threatens to undermine it all: <br>Those initial researchers and early architects of the Internet couldn’t possibly predict the scale and impact this network would eventually have.</p><blockquote><strong>As a result, the Internet just isn’t built to handle the enormous amount of data that is being distributed between billions of people and devices today.</strong></blockquote><p>Continuously increasing bandwidth needs put immense pressure on already strained and fragile infrastructure. And many of the current fixes have been duct taped on instead of driven by innovation.</p><p>To date, the predominant way of expanding the network has been through new investments in old solutions. Companies in North America and Western Europe have invested billions of dollars in burying cables in the ground, laying cables across the sea floor, and building data centers in the suburbs of western cities.</p><p>Yet problems such as network congestion, service downtime, <br>and performance issues stemming from a shortage of capacity are still part of the everyday Internet experience. We sometimes experience those as buffering during live streaming events, and delayed news sites during critical moments.</p><blockquote>That’s the state of the Internet today.</blockquote><blockquote>Now here’s where we see it going.</blockquote><p>Over the next five to ten years, <strong>the most rapid growth of Internet consumption and distribution will be seen in parts of the world where the current infrastructure hasn’t even caught up to the ailing status quo.</strong></p><p>The population in cities such as Nairobi and Mumbai are now demanding access to the same types of experiences that Internet users have learned to take for granted in the western world. And they shouldn’t have to wait for another 25 years for sufficient infrastructure to be put into place.</p><p>The picture doesn’t end there.</p><p>Not only is there explosive exponential growth in the number of people connecting to the Internet, but we are also facing a <strong>massive increase in the number of connected devices each person controls.</strong></p><p>By 2020, the numbers will be truly impressive.</p><p><a href="http://www.cisco.com/c/en/us/solutions/collateral/service-provider/visual-networking-index-vni/vni-hyperconnectivity-wp.html">Cisco predicts</a> that the number of devices connected to IP networks will be more than <em>three times</em> the global population. Every second, a <em>million </em>minutes of video content will cross the network. And VR and video will continue to represent an ever-growing portion of our content consumption.</p><p>The writing on the wall is clear: Internet infrastructure is facing substantial scale and performance challenges today, and those challenges will continue to grow over the next five to ten years.</p><blockquote>We founded Greta.io because we realized we could develop intelligent technology to help overcome these challenges.</blockquote><blockquote>So that’s what we did.</blockquote><p>Our technology enables developers and companies to provide substantially faster and better end-user experiences without costly upgrades to the underlying infrastructure of the network itself.</p><p>Our approach utilizes technologies such as <strong>artificial intelligence</strong> and <strong>machine learning</strong> to unlock <strong>enormous optimization gains.</strong> We create intelligent data routing based on global network data.</p><p>This is fundamental in building a dynamic network and provides a sustainable alternative to the old model of scaling by investing in static infrastructure. Our approach means that you can utilize existing infrastructure in a much smarter way. It allows the network to grow organically based on demand.</p><p>There is a tremendous opportunity in front of all of us today, because the Internet is nowhere close to being a “done deal.”</p><blockquote>Over half of the world’s population is still waiting to get connected. New devices and content formats are waiting to get invented and explored.</blockquote><p>At <a href="https://greta.io/">Greta.io</a>, we are passionate about this development, and we’re determined to find the optimal way to distribute all of that data.</p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8719e7cc53d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/internet-is-scaling-faster-than-todays-infrastructure-can-keep-up-e8719e7cc53d">Internet is scaling faster than today’s infrastructure can keep up</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Summary of GCP Next 2017]]></title>
            <link>https://medium.com/greta-io/the-last-keynote-was-all-about-openness-834fd09c9002?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/834fd09c9002</guid>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Lovisa Dahl]]></dc:creator>
            <pubDate>Sat, 11 Mar 2017 02:02:29 GMT</pubDate>
            <atom:updated>2017-09-13T13:19:35.248Z</atom:updated>
            <content:encoded><![CDATA[<p>The last keynote was all about openness. Sam Ranji opened the keynote with the word of this is the day for developers. Followed by Sarah Novotny, Program Manager of Kubernetes really making a point of how Kubernetes has evolved since it went open source. Jim Zemlin stated that <em>“all of us are smarter than any of us”</em> as the core benefit of open source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhnTJK95C0FsifweUnpw-Q.jpeg" /></figure><p>That statement really got emphasised by Vint Cerf, presenting how TCP and TLS has evolved and how the openness is tightly built in the Internet as it is today. From their first committee to the public open source code of every website today.</p><p><em>Innovation by collaboration</em> is really in core of Google and something they prove over and over again. Referring to our own experience, where we are contributing and discussing tightly with the developers of Spinnaker, Kubernetes and webRTC. And along the openness, Internet is made for everyone, but not yet accessible to anyone. That’s what we are aiming for. <em>The Internet as it is built today is not very scalable, there are obviously million positive things with the internet but it has limitations in its infrastructure today</em>, as our CEO <a href="https://medium.com/u/c0f67757f96f">Anna Ottosson</a> stated on stage today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WGwq2o2lADXuLcbt8AgD8w.jpeg" /></figure><p>Read more about our last few days at Google Cloud Next ’17 and what we’re excited about: <a href="https://blog.greta.io/highlights-from-diane-greenes-opening-of-google-next-2017-25bcbe6c3750#.ewbzkpjeb">Opening of GCP Next 2017</a> , <a href="https://blog.greta.io/why-were-excited-about-google-cloud-spanner-7905d47d7d0#.sg2i44vwj">Announcing Cloud Spanner</a>, <a href="https://blog.greta.io/highlights-from-keynote-day-2-by-urs-h%C3%B6lzle-at-googlenext17-162a5e6f3fe3#.uhs3yo8lw">Second Day of GCP Next</a></p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=834fd09c9002" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/the-last-keynote-was-all-about-openness-834fd09c9002">Summary of GCP Next 2017</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Highlights from keynote Day 2 by Urs Hölzle at #GoogleNext17]]></title>
            <link>https://medium.com/greta-io/highlights-from-keynote-day-2-by-urs-h%C3%B6lzle-at-googlenext17-162a5e6f3fe3?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/162a5e6f3fe3</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-spanner]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Lovisa Dahl]]></dc:creator>
            <pubDate>Fri, 10 Mar 2017 02:33:34 GMT</pubDate>
            <atom:updated>2017-09-13T13:20:14.704Z</atom:updated>
            <content:encoded><![CDATA[<p>Second day of GCP Next is opened by Urs Hölzle presenting the current state of GCP and hyped their recent announcement of Cloud Spanner. It really makes a point of how fast GCP has grown over the years, and how they’re making services out of what started out as internal systems. Like Hangout and Cloud Spanner. Let’s focus on the later one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I7f4zkPVLQq9Wrp89PrdZg.jpeg" /></figure><p>There’s been a lot of buzz around the Cloud Spanner lately. Only the fact that it’s running with 8 atomic clocks for delivering on consistency is a strong indicator of the ambition and effort put into it. What really struck me during the demo of Cloud Spanner is how well-formed the usage is. Comparing to, as Greg DeMichellie states, the hassle of configuring and maintaining a relational sequel database on the cost of either horizontally scaling or consistency. DeMichellie gives the example of ticket selling, you want to make sure to sell every ticket, and every ticket only once. What is really fascinating about the demo is how this piece of advanced revolutionary piece of software is offered and managed in a very neat and nice format. Changing the schema, adjusting the capacity is as easy as a few clicks in a nice UI.</p><p>With that said, I think Cloud Spanner is remarkable in at least two ways, first of all in what the database offer from a technical point of view. The second part, is how they could removing unwanted complexity from the configurations by building the software in a new way.</p><p><a href="https://greta.io/">Greta.io</a> is dedicated to helping users increase site performance via an innovative approach to content delivery. We use machine learning to make content routing decisions in the client based on real-time network data. For every piece of content, Greta automatically decides if the content should be delivered over multi-CDN, peer-to-peer, client cache or an overlay network. As a result, customers experience shorter content load times, higher content quality and server offload during peak traffic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=162a5e6f3fe3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/highlights-from-keynote-day-2-by-urs-h%C3%B6lzle-at-googlenext17-162a5e6f3fe3">Highlights from keynote Day 2 by Urs Hölzle at #GoogleNext17</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we’re excited about Google Cloud Spanner]]></title>
            <link>https://medium.com/greta-io/why-were-excited-about-google-cloud-spanner-7905d47d7d0?source=rss----3e1bf5de3afb---4</link>
            <guid isPermaLink="false">https://medium.com/p/7905d47d7d0</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[cloud-spanner]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[spanner]]></category>
            <dc:creator><![CDATA[Pierre Dubouilh]]></dc:creator>
            <pubDate>Thu, 09 Mar 2017 19:06:59 GMT</pubDate>
            <atom:updated>2017-07-11T09:18:03.101Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qeY0gUU25-xlaelGAqC-Gw.png" /></figure><p>At Greta, we’ve been very excited about Google Cloud Spanner for a long time — we read the <a href="https://static.googleusercontent.com/media/research.google.com/sv//archive/spanner-osdi2012.pdf">paper</a> about the ideas behind Spanner many years ago, and have been waiting for it to materialise ever since. For those of you not familiar with Spanner yet, it is Google’s new relational database service that they are now commercially launching during Google Next 2017. Eric Schmidt even said the following during his keynote on day 1:</p><blockquote>“Cloud Spanner is a piece of art in computer science” <em>Eric Schmidt</em></blockquote><p>One of the things that makes Spanner a pretty unique and exciting database is that it scales horizontally to thousand of servers with extremely low latency, meaning that it is capable of handling extremely high workloads. In combination with synchronous data replication it makes it the service very appealing for us at Greta as it enables us to do data replication in no time. However, what we’re truly thrilled about is the global version of Cloud Spanner which Google have announced will be out later during 2017, as that will enable us to do global data replication with close to no latency. In the sections below we’ll quickly outline some of the ways we’re looking to use the service.</p><p>The infrastructure we’ve used whilst waiting for Spanner relied on distributed local cache with one persistent datastore. While this solution allowed us to scale quickly, we ended up having to make a compromise when accessing the data;<br> — A short TTL on the cache allows for data to always be at the latest state, but it is at the expense of frequent requests to our persistent datastore which requires more time<br> — A longer TTL on the cache enables fewer requests to the persistent store, and hence is faster. However, a new state takes longer to be adopted.</p><p>It is difficult to find a right balance in the trade-off between speed and always having the correct state — which is why Spanner is such a compelling service. Spanner manages to provide both these aspects: globally distributed data that’s fast to access, and that is persistent. A bonus is that it allows us to use the same SQL version between BigQuery and Spanner.</p><p>The set-up was very fast, and as we were already using the <em>Node.js</em> Google Cloud Library, we had no further login to handle. We could use our new Spanner datastore directly, without having to handle any connection parameter. The web user interface is accessible throughout the console and that also ended up being very useful as we could perform live queries both for testing and for actual data.</p><p>Learn more about Spanner here: <a href="https://www.youtube.com/watch?v=IjqDC4WrAIQ">https://www.youtube.com/watch?v=IjqDC4WrAIQ</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7905d47d7d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greta-io/why-were-excited-about-google-cloud-spanner-7905d47d7d0">Why we’re excited about Google Cloud Spanner</a> was originally published in <a href="https://medium.com/greta-io">Greta.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>