DOCSLIB.ORG

Grpc Layer for Content Delivery in Kentico Kontent

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Grpc Layer for Content Delivery in Kentico Kontent Masaryk University Faculty of Informatics gRPC Layer for Content Delivery in Kentico Kontent Master’s Thesis Bc. Petra Rebrošová Brno, Spring 2021 Masaryk University Faculty of Informatics gRPC Layer for Content Delivery in Kentico Kontent Master’s Thesis Bc. Petra Rebrošová Brno, Spring 2021 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Bc. Petra Rebrošová Advisor: Bruno Rossi, PhD. i Acknowledgements First of all, I would like to thank my advisor Bruno Rossi, Ph.D. for his guidance, patience, providing valuable feedback and advice during the writing of this thesis. Secondly, I would like to thank my consultant Petr Švihlík for his advice and help with technical issues. Furthermore, I want to express my gratitude to my family, friends, and colleagues from Kentico for their unconditional support, patience, motivation and always being there for me. Finally, I would like to thank my partner Jakub for his support and always standing by me. iii Abstract Remote Procedure Calls (RPCs) have been popular throughout the history of machine-to-machine network communication from its beginning. gRPC protocol is a new concept of RPC invented by Google, which promises more efficient messages and their faster transfer. Ken- tico Kontent, as a Content Management System (CMS), can benefit from the utilization of gRPC in alternative content delivery to its cur- rent APIs. Because Kentico Kontent is widely used and it is essential to pro- vide as fast data transfer between client applications and Kontent as possible, it is important always to search for alternative solutions that would improve content delivery. The goals of this thesis are to analyze gRPC in line with relevant studies and documentation and evaluate it using Goal Question Metric (GQM) methodology. The results show that gRPC excels in scenarios where mobile or IoT application acts as a client, that can be also used in the omnichannel content delivery scenarios viable for Kontent. After that, a gRPC content delivery layer was designed and built as an alternative endpoint for Kontent’s Delivery API, within a sample mobile application processing the data from the implemented gRPC API endpoint. Results of the analysis prove that gRPC significantly reduces size of the messages. In scenarios with a large payload the gRPC messages are faster than the originally used HTTP messages, however, it does not apply for messages with a small payload. iv Keywords gRPC, Kentico Kontent, Content Management System, Protocol Buffer, API, .NET, REST v Contents 1 Introduction 3 1.1 Problem Statement ......................3 1.2 Thesis Goals ..........................4 1.3 Thesis Structure ........................5 2 Delivering Content in Kentico Kontent 7 2.1 Content Management System ................7 2.1.1 Headless CMS . .7 2.2 Software Delivery .......................9 2.2.1 Software-as-a-Service Paradigm . .9 2.2.2 Content-as-a-Service Paradigm . .9 2.3 Omnichannel vs. Multichannel Approach .......... 10 2.3.1 Multichannel approach . 10 2.3.2 Omnichannel Approach . 10 2.4 Content Delivery in Kentico Kontent ............. 10 2.4.1 APIs . 11 2.4.2 SDK . 13 2.4.3 Delivered Data Structures . 14 2.5 Possible Improvements for Content Delivery ......... 15 2.6 Summary ........................... 15 3 Remote Communication 17 3.1 History of Remote Communication .............. 17 3.1.1 Beginnings of Networks and Remote Commu- nication . 17 3.1.2 World Wide Web . 19 3.1.3 Web 1.0 . 20 3.1.4 Web 2.0 . 20 3.1.5 Web 3.0 . 20 3.1.6 Web 4.0 and the Future of Web . 21 3.2 Remote Communication Protocols and Frameworks ..... 21 3.2.1 REST . 21 3.2.2 HTTP . 21 3.2.3 RPC . 23 3.2.4 gRPC . 23 vii 3.3 Summary ........................... 24 4 gRPC 25 4.1 Comparison of gRPC and REST ............... 25 4.2 Design ............................. 25 4.2.1 Network Communication Principle . 26 4.2.2 Types of Communication . 26 4.2.3 Error Handling . 28 4.3 Usability of gRPC ....................... 29 4.3.1 Microservices . 29 4.3.2 Web Applications and Websites . 29 4.3.3 Mobile Applications . 30 4.3.4 IoT and Embedded Systems . 31 4.4 Requirements and Principles ................. 32 4.5 Performance .......................... 33 4.5.1 Battery Consumption . 34 4.5.2 Speed of the Requests . 34 4.6 Security ............................ 35 4.6.1 Authentication . 35 4.6.2 Vulnerabilities . 36 4.7 Reliability ........................... 37 4.8 Developer Experience ..................... 37 4.9 gRPC Utilization in Implementation ............. 40 4.9.1 Protocol Buffer . 40 4.9.2 Data Serialization and JSON Mapping . 41 4.9.3 Network Communication . 43 4.10 Summary ........................... 43 5 gRPC Analysis 45 5.1 The Goal Question Metric Approach ............. 45 5.2 Stated GQM .......................... 45 5.3 Evaluation of the Stated GQMs ................ 47 5.3.1 G1: Analyze and find the most suitable types of applications for gRPC protocol, viable for om- nichannel content delivery. 48 5.3.2 G2: Show performance benefits of using gRPC in comparison with HTTP. 50 viii 5.3.3 G3: Show Developer experience (DX) benefits of utilizing gRPC . 51 51subsection.5.3.4 5.4 Summary ........................... 53 6 gRPC Layer for Kentico Kontent 55 6.1 Migration from REST Architecture to gRPC ......... 55 6.2 Design of gRPC Content Delivery Layer in Kentico Kontent 56 6.2.1 Models . 56 6.3 API Implementation Details ................. 56 6.4 Server Application Run .................... 57 6.5 Client Application ...................... 57 6.6 Experiments .......................... 59 6.6.1 Server Device Details . 59 6.6.2 Measurements . 59 6.7 Analysis of gRPC Integration into Kentico Kontent Deliv- ery API ............................ 61 6.7.1 Stated GQM . 61 6.7.2 Evaluation of the Stated GQMs . 62 6.7.3 Conclusion of the Analysis of the Experimental Work......................... 63 6.8 Summary ........................... 63 7 Conclusion 65 7.1 Results of the Thesis Goals .................. 65 7.2 Future Work .......................... 66 Bibliography 67 A Electronic Attachments 75 B Utilized Tools and Configurations 77 B.1 C# Implementation of gRPC API ............... 77 B.2 Client Android Application .................. 77 B.3 API Testing .......................... 78 C Sample Code 79 C.1 items_service.proto ...................... 79 ix D Mobile Application Details 81 D.1 Application Screenshots .................... 82 x List of Tables 4.1 REST HTTP API and gRPC API overview (based on comparison from [46]) 39 5.1 Evaluation of GQM metrics for G1 49 5.2 Average times of gRPC and HTTP messages 50 5.3 Evaluation of GQM metrics for G3 52 5.4 Evaluation of GQM metrics for G4 53 6.1 Size of gRPC and HTTP requests and responses containing 10, 100, or 500 items retrieved from GetItems endpoints 60 6.2 Median of the measured speed of responses containing 10, 100, or 500 items retrieved from gRPC and HTTP GetItems endpoints 60 xi List of Figures 1.1 Thesis structure with highlighted thesis goals 4 2.1 Headless CMS structure, adapted from [5] 8 2.2 Kentico Kontent public APIs structure 12 4.1 Structure of gRPC on HTTP/2 27 5.1 Scheme of GQM approach 46 6.1 Structure of gRPC and HTTP Kentico Kontent Delivery API communicating locally with client mobile application 58 6.2 Comparison of execution times of gRPC and HTTP messages 61 D.1 Main screen of the implemented Android application 82 D.2 Screen of the implemented Android application displaying data from gRPC and HTTP GetItems endpoints 83 xiii Acronyms 6LoWPAN IPv6 over Low-Power Wireless Personal Area Networks. ALTS Application Layer Transport Security. API Application programming interface. CaaS Content-as-a-Service. CDN Content delivery network. CMS Content Management System. CRM Customer Relationship Management. CVSS Common Vulnerability Scoring System. DX Developer experience. ERP Enterprise Resource Planning. ESP Extensible Server Proxy. FTP File Transfer Protocol. GQM Goal Question Metric. gRPC gRPC Remote Procedure Calls. HTTP HyperText Transfer Protocol. IaaS Infrastructure-as-a-Service. IDL Interface Definition Language. IoT Internet of Things. IP Internet Protocol. IXP Internet exchange point. 1 Acronyms JWT JSON Web Token. LWM2M OMA Lightweight M2M. MQTT Message Queuing Telemetry Transport. NVD National Vulnerability Database. PaaS Platform-as-a-Service. QoS Quality-of-Service. REST Representational state transfer. RFID Radio-frequency identification infrastructure. RPC Remote Procedure Calls. SaaS Software-as-a-Service. SDK Software development kit. SLA Service-level agreement. SSL/TLS Secure Sockets Layer/Transport Layer Security. TCP Transmission Control Protocol. TLS Transport Layer Security. 2 1 Introduction In today‘s world, the number of electronic devices around us increases every day and a huge amount of data is stored and sent through the network. These devices communicate with us or with each other, they process, share or display the data. When analyzing services and applications according to their toler- ance for data loss, need for high-speed, etc., different kinds of services have different demands. There is also a difference in requirements of web, mobile, or IoT applications. A number of communication frameworks and protocols guaranteeing the fulfillment of the specific demands increase. Redesign of the product architecture or utilization of new protocols and frameworks may bring an opportunity for en- hancement, for example in the speed of the message exchange in the communication. Kentico Kontent as Content Management System (CMS) is one of several approaches to managing and providing data. For CMS it is not important only to manage and store data, but also provide data to the various systems and applications reliably and with as minimal network latency as possible [1].
Load more

Recommended publications
  • Advanced Model Deployments with Tensorflow Serving Presentation.Pdf
    Most models don’t get deployed. Hi, I’m Hannes. An inefficient model deployment import json from flask import Flask from keras.models import load_model from utils import preprocess model = load_model('model.h5') app = Flask(__name__) @app.route('/classify', methods=['POST']) def classify(): review = request.form["review"] preprocessed_review = preprocess(review) prediction = model.predict_classes([preprocessed_review])[0] return json.dumps({"score": int(prediction)}) Simple Deployments @app.route('/classify', methods=['POST']) Why Flask is insufficient def classify(): review = request.form["review"] ● No consistent APIs ● No consistent payloads preprocessed_review = preprocess(review) ● No model versioning prediction = model.predict_classes( ● No mini-batching support [preprocessed_review])[0] ● Inefficient for large models return json.dumps({"score": int(prediction)}) Image: Martijn Baudoin, Unsplash TensorFlow Serving TensorFlow Serving Production ready Model Serving ● Part of the TensorFlow Extended Ecosystem ● Used internally at Google ● Highly scalable model serving solution ● Works well for large models up to 2GB TensorFlow 2.0 ready! * * With small exceptions Deploy your models in 90s ... Export your Model import tensorflow as tf TensorFlow 2.0 Export tf.saved_model.save( ● Consistent model export model, ● Using Protobuf format export_dir="/tmp/saved_model", ● Export of graphs and signatures=None estimators possible ) $ tree saved_models/ Export your Model saved_models/ └── 1555875926 ● Exported model as Protobuf ├── assets (Saved_model.pb)
    [Show full text]
  • An Evaluation of Tensorflow As a Programming Framework for HPC Applications
    DEGREE PROJECT IN COMPUTER SCIENCE AND ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2018 An Evaluation of TensorFlow as a Programming Framework for HPC Applications WEI DER CHIEN KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE An Evaluation of TensorFlow as a Programming Framework for HPC Applications WEI DER CHIEN Master in Computer Science Date: August 28, 2018 Supervisor: Stefano Markidis Examiner: Erwin Laure Swedish title: En undersökning av TensorFlow som ett utvecklingsramverk för högpresterande datorsystem School of Electrical Engineering and Computer Science iii Abstract In recent years, deep-learning, a branch of machine learning gained increasing popularity due to their extensive applications and perfor- mance. At the core of these application is dense matrix-matrix multipli- cation. Graphics Processing Units (GPUs) are commonly used in the training process due to their massively parallel computation capabili- ties. In addition, specialized low-precision accelerators have emerged to specifically address Tensor operations. Software frameworks, such as TensorFlow have also emerged to increase the expressiveness of neural network model development. In TensorFlow computation problems are expressed as Computation Graphs where nodes of a graph denote operation and edges denote data movement between operations. With increasing number of heterogeneous accelerators which might co-exist on the same cluster system, it became increasingly difficult for users to program efficient and scalable applications. TensorFlow provides a high level of abstraction and it is possible to place operations of a computation graph on a device easily through a high level API. In this work, the usability of TensorFlow as a programming framework for HPC application is reviewed.
    [Show full text]
  • From XML to Flat Buffers: Markup in the Twenty-Teens Warning! the Contenders
    Elliotte Rusty Harold [email protected] August 2018 From XML to Flat Buffers: Markup in the Twenty-teens Warning! The Contenders ● XML ● JSON ● YAML ● EXI ● Protobufs ● Flat Protobufs XML JSON YAML EXI Protobuf Flat Buffers App Engine X X Standard Java App Engine X Flex What Uses What Kubernetes X X From technology, tools, and systems Eclipse X I use frequently. There are many others. Maven X Ant X Google X X X X X “APIs” Publishing X XML XML ● Very well defined standard ● By far the most general format: ○ Mixed content ○ Attributes and elements ● By far the best tool support. Nothing else is close: ○ XSLT ○ XPath ○ Many schema languages: ■ W3C XSD ■ RELAX NG More Reasons to Choose XML ● Most composable for mixing and matching markup; e.g. MathML+SVG in HTML ● Does not require a schema. ● Streaming support: very large documents ● Better for interchange amongst unrelated parties ● The deeper your needs the more likely you’ll end up here. Why Not XML? ● Relatively complex for simple tasks ● Limited to no support for non-string programming types: ○ Numbers, booleans, dates, money, etc. ○ Lists, maps, sets ○ You can encode all these but APIs don’t necessarily recognize or support them. ● Lots of sharp edges to surprise the non-expert: ○ 9/10 are namespace related ○ Attribute value normalization ○ White space ● Some security issues if you’re not careful (Billion laughs) JSON ● Simple for object serialization and program data. If your data is a few basic types (int, string, boolean, float) and data structures (list, map) this works well. ● More or less standard (7-8 of them in fact) ● Consumption libraries for essentially all significant languages Why Not JSON? ● It is surprising how fast needs grow past a few basic types and data structures.
    [Show full text]
  • Trifacta Data Preparation for Amazon Redshift and S3 Must Be Deployed Into an Existing Virtual Private Cloud (VPC)
    Install Guide for Data Preparation for Amazon Redshift and S3 Version: 7.1 Doc Build Date: 05/26/2020 Copyright © Trifacta Inc. 2020 - All Rights Reserved. CONFIDENTIAL These materials (the “Documentation”) are the confidential and proprietary information of Trifacta Inc. and may not be reproduced, modified, or distributed without the prior written permission of Trifacta Inc. EXCEPT AS OTHERWISE PROVIDED IN AN EXPRESS WRITTEN AGREEMENT, TRIFACTA INC. PROVIDES THIS DOCUMENTATION AS-IS AND WITHOUT WARRANTY AND TRIFACTA INC. DISCLAIMS ALL EXPRESS AND IMPLIED WARRANTIES TO THE EXTENT PERMITTED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE AND UNDER NO CIRCUMSTANCES WILL TRIFACTA INC. BE LIABLE FOR ANY AMOUNT GREATER THAN ONE HUNDRED DOLLARS ($100) BASED ON ANY USE OF THE DOCUMENTATION. For third-party license information, please select About Trifacta from the Help menu. 1. Quick Start . 4 1.1 Install from AWS Marketplace . 4 1.2 Upgrade for AWS Marketplace . 7 2. Configure . 8 2.1 Configure for AWS . 8 2.1.1 Configure for EC2 Role-Based Authentication . 14 2.1.2 Enable S3 Access . 16 2.1.2.1 Create Redshift Connections 28 3. Contact Support . 30 4. Legal 31 4.1 Third-Party License Information . 31 Page #3 Quick Start Install from AWS Marketplace Contents: Product Limitations Internet access Install Desktop Requirements Pre-requisites Install Steps - CloudFormation template SSH Access Troubleshooting SELinux Upgrade Documentation Related Topics This guide steps through the requirements and process for installing Trifacta® Data Preparation for Amazon Redshift and S3 through the AWS Marketplace.
    [Show full text]
  • Cloud Native Communication Patterns with Grpc
    Cloud Native Communication Patterns with gRPC Kasun Indrasiri Author “gRPC Up and Running” and “Microservices for Enterprise” About Me ● Author “gRPC Up & Running”, “Microservices for Enterprise” ● Product Manager/Senior Director at WSO2. ● Committer and PMC member at Apache Software Foundation. ● Founder “Bay area Microservices, APIs and Integration” meetup group. What is gRPC? ● Modern Inter-process communication technology. ● Invoking remote functions as easy as making a local function invocation. ● Contract-first. ● Binary messaging on the wire on top of HTTP2 ● Polyglot. Fundamentals of gRPC - Service Definition syntax = "proto3"; ● Defines the business capabilities of package ecommerce; your service. service ProductInfo { rpc addProduct(Product) returns (ProductID); ● Protocol Buffers used as the IDL for rpc getProduct(ProductID) returns (Product); define services. } message Product { ● Protocol Buffers : string id = 1; ○ A language-agnostic, platform-neutral, string name = 2; extensible mechanism to serializing string description = 3; float price = 4; structured data. } ● Defines service, remote methods, and message ProductID { data types. string value = 1; } ProductInfo.proto Fundamentals of gRPC - gRPC Service // AddProduct implements ecommerce.AddProduct ● gRPC service implements the func (s *server) AddProduct(ctx context.Context, in *pb.Product) (*pb.ProductID, business logic. error) { ● Generate server side skeleton from // Business logic } service definition. // GetProduct implements ecommerce.GetProduct func (s *server) GetProduct(ctx
    [Show full text]
  • Integrating R with the Go Programming Language Using Interprocess Communication
    Integrating R with the Go programming language using interprocess communication Christoph Best, Karl Millar, Google Inc. [email protected] Statistical software in practice & production ● Production environments !!!= R development environment ○ Scale: machines, people, tools, lines of code… ● “discipline of software engineering” ○ Maintainable code, common standards and processes ○ Central problem: The programming language to use ● How do you integrate statistical software in production? ○ Rewrite everything in your canonical language? ○ Patch things together with scripts, dedicated servers, ... ? Everybody should just write Java! Programming language diversity ● Programming language diversity is hard … ○ Friction, maintenance, tooling, bugs, … ● … but sometimes you need to have it ○ Many statistics problems can “only” be solved in R* ● How do you integrate R code with production code? ○ without breaking production *though my colleagues keep pointing out that any Turing-complete language can solve any problem The Go programming language ● Open-source language, developed by small team at Google ● Aims to put the fun back in (systems) programming ● Fast compilation and development cycle, little “baggage” ● Made to feel like C (before C++) ● Made not to feel like Java or C++ (enterprise languages) ● Growing user base (inside and outside Google) Integration: Intra-process vs inter-process ● Intra-process: Link different languages through C ABI ○ smallest common denominator ○ issues: stability, ABI evolution, memory management, threads, … Can we do better? Or at least differently? ● Idea: Sick of crashes? Execute R in a separate process ○ Runs alongside main process, closely integrated: “lamprey” ● Provide communication layer between R and host process ○ A well-defined compact interface surface Integration: Intra-process vs inter-process C runtime Go R RPC client C++ runtime IPC Messages Java (library) Python RPC server ..
    [Show full text]
  • SESSION 2 YANG, Openconfig, and Gnmi
    SESSION 2 YANG, OpenConfig, and gNMI Copyright © 2019 - Open Networking Foundation Session 2 Overview 1. YANG: Configuration Modeling Language 2. OpenConfig: Configuration and telemetry model instances 3. gNMI: Runtime Configuration and Monitoring Interface 4. gNOI: Runtime Operations Interface Copyright © 2019 - Open Networking Foundation YANG Overview YANG is a data modeling language for network configuration ● Used to express the structure of data, NOT the data itself ● Instances of data can be expressed in XML, JSON, Protobuf, etc. and are considered valid if they adhere to the YANG data model (schema) From a YANG model, we care about 2 things: 1. Data tree organization (from which we get the paths and leaf data types) 2. Semantics of the leaf nodes (from the description field, usually in English) History: YANG was originally designed as a data modeling language for NETCONF. It borrows the syntactic structure and base types from SMIng, which is an evolution of SMI, the data modeling language for SNMP used for MIBs. Copyright © 2019 - Open Networking Foundation YANG Module A module is a self-contained tree of nodes. Modules are the smallest unit that can be “compiled” by YANG tools. // A module is a self-contained tree of nodes module demo-port { A module contains: // YANG Boilerplate ● boilerplate, like a namespace, yang-version "1"; prefix for reference in other namespace "https://opennetworking.org/yang/demo"; modules, description, version / prefix "demo-port"; description "Demo model for managing ports"; revision history, etc. revision "2019-09-10" { ● identities and derived types description "Initial version"; ● modular groupings reference "1.0.0"; } ● a top-level container that defines tree of data nodes // ..
    [Show full text]
  • Almond Variety Detection Using Deep Learning
    Almond Variety Detection using Deep Learning Benarous Ahmed Omar Farouq - a41369 Thesis presented to the School of Technology and Management in the scope of the Master in Information Systems. Supervisors: Prof. Maria João Tinoco Varanda Pereirar This document does not include the suggestions made by the board. Bragança 2019-2020 Dedication I dedicate my dissertation work to my family. A special feeling of gratitude to my loving parents, whose words of encouragement and push for tenacity ring in my ears. I also dedicate this dissertation to my many friends who have supported me throughout the process. I will always appreciate all they have done. v Acknowledgment In the name of Allah, the Most Gracious, the Most Merciful I would like to express my deep sense of gratitude, respect and heartfelt thanks to Prof. Maria João Tinoco Varanda Pereira, for her great contribu- tions, encouragement and support during the thesis writing, understanding and patience that have accompanied me during the research time. I would like to acknowledge and thank to ESTIG-IPB school division for providing me of the necessary materials needed to conduct my research and providing any assistance requested. I would like to acknowledge and thank to ESA-IPB school division for allow- ing me to conduct my research and providing any assistance requested. Special thanks goes to the members of the lab Professors Nuno Rodrigues and José Alberto Pereira for their continued support. Finally I would like to thank all professor of the hassiba benbouali university where i have started my journey of studying computer science. And special thank and acknowledgment to all community of computer science, this dynamic and healthy community is the reason why computer science, which is very new vi field compared to other sciences, has evolved so dramatically fast and now have huge impact on almost everything.
    [Show full text]
  • Developing the Guidelines for Migration from Restful Microservices to Grpc
    Masaryk University Faculty of Informatics Developing the guidelines for migration from RESTful microservices to gRPC Master’s Thesis Michal Štefanič Brno, Spring 2021 Masaryk University Faculty of Informatics Developing the guidelines for migration from RESTful microservices to gRPC Master’s Thesis Michal Štefanič Brno, Spring 2021 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Michal Štefanič Advisor: RNDr. Josef Spurný i Acknowledgements I would like to thank my advisors, RNDr. Josef Spurný for his time and valuable consultations, and doc. Mouzhi Ge, Ph.D. who left the university, but still found a time for thesis consultations. I would also like to thank the colleagues from Kiwi.com, especially Matouš Dziviak with whom I consulted a lot of technical questions related to the thesis. And Tomáš Gerich for proofreading the thesis. ii Abstract With the rising popularity of microservice architecture, Google de- cided to revive the "Remote procedure call" (RPC) concept to facili- tate effective communication between single services and developed their own framework (gRPC) for RPC service communication. gRPC became quickly popular and many famous companies as Netflix, Mi- crosoft, Slack integrated it into their systems. However, there is not a clear, step-by-step guide on when and how to migrate your services to gRPC architecture.
    [Show full text]
  • Code Smell Prediction Employing Machine Learning Meets Emerging Java Language Constructs"
    Appendix to the paper "Code smell prediction employing machine learning meets emerging Java language constructs" Hanna Grodzicka, Michał Kawa, Zofia Łakomiak, Arkadiusz Ziobrowski, Lech Madeyski (B) The Appendix includes two tables containing the dataset used in the paper "Code smell prediction employing machine learning meets emerging Java lan- guage constructs". The first table contains information about 792 projects selected for R package reproducer [Madeyski and Kitchenham(2019)]. Projects were the base dataset for cre- ating the dataset used in the study (Table I). The second table contains information about 281 projects filtered by Java version from build tool Maven (Table II) which were directly used in the paper. TABLE I: Base projects used to create the new dataset # Orgasation Project name GitHub link Commit hash Build tool Java version 1 adobe aem-core-wcm- www.github.com/adobe/ 1d1f1d70844c9e07cd694f028e87f85d926aba94 other or lack of unknown components aem-core-wcm-components 2 adobe S3Mock www.github.com/adobe/ 5aa299c2b6d0f0fd00f8d03fda560502270afb82 MAVEN 8 S3Mock 3 alexa alexa-skills- www.github.com/alexa/ bf1e9ccc50d1f3f8408f887f70197ee288fd4bd9 MAVEN 8 kit-sdk-for- alexa-skills-kit-sdk- java for-java 4 alibaba ARouter www.github.com/alibaba/ 93b328569bbdbf75e4aa87f0ecf48c69600591b2 GRADLE unknown ARouter 5 alibaba atlas www.github.com/alibaba/ e8c7b3f1ff14b2a1df64321c6992b796cae7d732 GRADLE unknown atlas 6 alibaba canal www.github.com/alibaba/ 08167c95c767fd3c9879584c0230820a8476a7a7 MAVEN 7 canal 7 alibaba cobar www.github.com/alibaba/
    [Show full text]
  • Angularjs Controller Request Parameters
    Angularjs Controller Request Parameters Clyde daunts her Urtext interdentally, adjuvant and rhizomorphous. Prepared Nikki sometimes reappear his expiations touchingly and repaginate so atomistically! Midship and bubbly Barde flats irreverently and disestablish his gasifier provisorily and banefully. Topic names and descriptions for each course. Rather Provide The Parameters At Resolution Time, will execute the post on the network. URL and the route. Here, we now have a simple, How would you get Google Alerts information into a database other than to parse the text of the email message that Google sends you? If we want to add multiple parameters, instead of reloading the entire page. No more posts to show. However, We Will Export These Data In Excel Sheet. Get practical advice to start your career in programming! Because this data is known, and the function body. Everytime a property of the controller changes, you will add reference links to the various available routes in your application. It has a name field which is initially null. We have another great solution. We can get HTTP status code of the response. Well, where we have the big advantage of providing deep links to our app through the URL. This second JS file will provide the services functionality of calling the RESTFul service. Find this content useful? In this example I have used simple test code where you would normally put your service logic to load items from the server or resolve other required data for your controller. Swallow errors for now. Consider the code snippet below. PATCH, this is not a good practice since Data Access gets complex as the application grows.
    [Show full text]
  • Faasten Your Decisions: Classification Framework And
    FaaSten Your Decisions: Classification Framework and Technology Review of Function-as-a-Service Platforms Vladimir Yussupova, Jacopo Soldanib, Uwe Breitenb¨uchera, Antonio Brogib, Frank Leymanna aInstitute of Architecture of Application Systems, University of Stuttgart, Germany bDepartment of Computer Science, University of Pisa, Italy Abstract Function-as-a-Service (FaaS) is a cloud service model enabling developers to offload event-driven executable snippets of code. The execution and management of such functions becomes a FaaS provider's responsibility, hereby included their on-demand provisioning and automatic scaling. Key enablers for this cloud service model are FaaS platforms, e.g., AWS Lambda, Microsoft Azure Functions or OpenFaaS. At the same time, the choice of the most appropriate FaaS platform for deploying and running a serverless application is not trivial, as various organizational and technical aspects have to be taken into account. In this work, we present (i) a FaaS platform classification framework derived using a mixed method study and (ii) a systematic technology review of the ten most prominent FaaS platforms, based on the proposed classification framework. Moreover, we present (iii) a FaaS platform selection support system, called FaaStener, which helps researchers and practitioners to choose the FaaS platform most suited for their requirements. Keywords: Serverless, Function-as-a-Service, FaaS, Platform, Classification Framework, Technology Review 1. Introduction The FaaS service model started gaining a lot of atten- tion after the release of AWS Lambda [4] in 2015, which In the context of cloud computing, the term server- started the overall serverless trend. Afterwards, all major less is typically used to describe a paradigm focusing on cloud providers introduced their FaaS offerings including cloud architectures that comprise provider-managed com- notable examples such as Microsoft Azure Functions [5], ponents [1].
    [Show full text]