CC BY
13
HOW TO DELIVER CONTENT TO END USERS WITH GCM Duc B.1, Thao L.2, Hieu L.3, Khoe N.4, Thuong T.5, Uyen V.6 (Russian Federation)
1Duc Bui - Master's Degree student, SOFTWARE DEVELOPMENT DEPARTMENT; 2Thao Le - Student, DEPARTMENT OF GEOINFORMATION SYSTEMS, FACULTY OF INFOCOMMUNICATION TECHNOLOGIES; 3Hieu Le - Student; 4Khoe Nguyen - Student, DEPARTMENT OF SECURE INFORMATION TECHNOLOGIES, FACULTY OF INFORMATION SECURITY AND COMPUTER TECHNOLOGIES; 5Thuong Tran Thi - Student, DEPARTMENT OF COMPUTER SYSTEM DESIGN AND SECURITY, FACULTY OF INFORMATION SECURITY AND COMPUTER TECHNOLOGIES;
6Uyen Vu - Student, DEPARTMENT OF IT IN THE FUEL AND ENERGY INDUSTRY, FACULTY OF LASER AND LIGHT ENGINEERING, SAINT-PETERSBURG NATIONAL RESEARCH UNIVERSITY OF INFORMATION TECHNOLOGIES, MECHANICS AND OPTICS, SAINT PETERSBURG
Abstract: GCM - is a service delivery Instant Messaging. An alternative to standard polling and a long polling, but not exclude, but rather complement them. Guarantees that the message will be delivered Google does not (although the reliability and speed of delivery has become a space in comparison with the ancestor C2DM). If the phone is off the Internet, the message will be stored in the GCM server up to 4 weeks. Ie, if the user has turned off the phone, went on vacation, he can not get a message on arrival. Therefore, GCM should work only with reliable means of delivery. Keywords: content, user, internet, application, network.
КАК ПРЕДОСТАВИТЬ КОНТЕНТ КОНЕЧНЫМ ПОЛЬЗОВАТЕЛЯМ С ПОМОЩЬЮ GCM Дык Б. М.1, Тхао Л. Д.2, Хиеу Л. В.3, Кхое Н. Х.4, Тхыонг Ч. Т. М.5, Уиен В. Т. Ф.6 (Российская Федерация)
1Дык Буй Минь - магистрант, кафедра программных систем; 2Тхао Ле Дык- студент, кафедра геоинформационных систем, факультет инфокоммуникационных технологий;
3Хиеу Ле Ван - студент; 4Кхое Нгуен Хыу - студент, кафедра безопасных информационных технологий, факультет информационной безопасности и компьютерных технологий; 5Тхыонг Чан Тхи Май - студент, кафедра проектирования и безопасности компьютерных систем, факультет информационной безопасности и компьютерных технологий; 6Уиен Ву Тхи Фыонг - студент, кафедра информационных технологий топливно-энергетического комплекса, факультет лазерной и световой инженерии, Санкт-Петербургский национальный исследовательский университет информационных технологий, механики и оптики, г. Санкт-Петербург
Аннотация: GCM - это сервис доставки мгновенных сообщений. Альтернатива стандартным polling и long polling, но не исключающая, а дополняющая их.
European science № 2(24) ■ 20
Гарантии, что сообщение будет доставлено, Гугл не дает (хотя надежность и скорость доставки стала просто космической по сравнению с предком C2DM). Если на телефоне интернет выключен, то сообщение будет храниться на GCM сервере до 4-х недель. Т.е. если пользователь выключил телефон, уехал в отпуск, то по приезду сообщение он может уже не получить. Поэтому GCM должен работать только вместе с надежными способами доставки.
Ключевые слова: контент, пользователь, интернет, приложение, сеть.
In this article, I will tell you about some great ways for you to deliver massive quantities of content to your end users in the most efficient performant way possible. Now imagine you've got a killer application running in the cloud and millions of users are using your application. Maybe that application is serving high definition videos of cats, or perhaps the latest audio for some cool new indie bands, or very likely, a boatload of HTML, JavaScript, CSS, or other. You've got tons of content to serve to your users. And those users are accustomed to getting their content fix in milliseconds. How are you going to give your users the experience they demand? You're faced with a number of challenges when it comes to serving large amounts of content to your users.
First, your users are located all over the place. But the servers running your application may not be located where your users are. How are you going to minimize the latency for your end users? How can you make sure that the video you are serving to them will actually start playing in two seconds? Second, content incurs internet egress charges. These are fees that you have to pay for transferring data from the infrastructure running your application to your end users. When the amount of content you serve increases in terms of size, quantity, and number of users consuming it, these fees could really add up. Third, you want to make sure that the performance experienced by your end users is unparalleled. You don't want them to have to wait while a page loads or constantly have video buffer on them. Finally, you want to make sure that your content is served 24/7. You need to make sure that when a user is using your application, the content is actually there and not being hit with errors [1].
Developers and infrastructure folks deal with these challenges every day and have leveraged content delivery networks to help overcome them. So what is a content delivery network (CDN)? CDN providers offer a means to push and cache your content as close to your users as possible. By leveraging relationships with ISPs, a CDN provider often has many points of presence near your end users. This helps minimize latency to content and reduces the amount of network egress traffic from your origin servers since the data is now being served at the edge. With such a high number of points of presence, you also ensure high availability and optimal performance for your end users. So how can you leverage CDNs with Google Cloud Platform to get your content to your users as quickly and reliably as possible? One way to achieve this is to leverage Google's global CDN when storing content in Google Cloud Storage. This is a fantastic way to get content as close to your end users as possible. Google has a vast network of edge locations. Google Cloud Storage essentially behaves like a CDN without any work on your part because publicly readable objects are, by default, cached in the Google Cloud Storage network. You can leverage Google Cloud Storage to serve content like video, audio, pictures, or your entire web application, provided that your data is publicly accessible. Another option would be to leverage Fastly as your CDN. Fastly is a world class CDN provider that directly connects with Google's backbone via Google Cloud Interconnect. This means that Fastly offers customers phenomenal performance and lower latency to content. The Fastly Cloud Accelerator provides a direct connection between their origin shield points of presence to Google's backbone, allowing Fastly to accelerate any content on Google Cloud Storage, Google Compute Engine, or Google App Engine to the user. When a user first makes a request for content, the application attempts to fetch the content from the Fastly edge cache at the edge of the network. If it's not there, it then requests the content from Fastly's origin servers, which are directly connected to Google's backbone. If the content is not on the
21 ■ European science № 2(24)
origin server, the content is fetched from the origin server sitting on Google Cloud Platform. From there, the content is then delivered to the end user and cached on the origin server and the edge cache server. When subsequent requests hit the edge cache in the future, the content will be there already. If content was requested from an edge node that doesn't have that content in the cache, it will fetch it from the Fastly origin servers [2].
Now another option for disseminating your content would be to leverage services offered by Wix. Wix provides technology built on top of Google Cloud Platform for creating web applications in the cloud. Wix also offers a set of services under the Wix Media Platform for storing, serving, uploading, and managing image, audio, and video files. These include services for manipulating and storage of images, transcoding, conversion, and storage of audio and video. These services are available via an SDK with Google Cloud Platform so you can leverage the services directly within your applications.
In order to best serve your content from Wix to your end users, Wix offers the ability to add a CDN for distributing your content managed by Wix to the edge for optimal latency, improved app performance, and overall improved experience for your end users. Whether you're running a simple website heavy on text and imagery or you're serving video and audio to your end customers, leveraging a CDN is a great option to consider. You will improve the overall performance of your application, thus improving the experience for your end users by getting content to them in a speedy and consistent fashion. You'll often reduce costs by reducing the amount of outgoing traffic from your origin servers and offloading that traffic to the CDN. And you'll provide added redundancy and resiliency in case of outages or system failures. Now you know how to best deliver your content on Google Cloud Platform to your end customers.
Список литературы /References
1. Messaging Concepts and Options. [Электронный ресурс]. Режим доступа: https://developers.google.com/cloud-messaging/concept-options/ (дата обращения: 11.10.2016).
2. Migration from C2DM. [Электронный ресурс]. Режим доступа: https://developers.google.com/cloud-messaging/c2dm/ (дата обращения: 13.09.2016).
Список литературы на английском языке /References in English
1. Messaging Concepts and Options. [Electronic resource]. URL: https://developers.google.com /cloud-messaging/concept-options/ (date of access: 11.10.2016).
2. Migration from C2DM. [Electronic resource]. URL: https://developers.google.com/cloud-messaging/c2dm/ (date of access: 13.09.2016).
European science № 2(24) ■ 22
