scholarly journals A Novel Data Analysis Service Oriented Architecture Using R Statistics Engine

2012 ◽  
Author(s):  
Rich LEE
Keyword(s):  
Data Analysis ◽  
Service Oriented Architecture ◽  
Service Oriented

Data Analysis for Potential Reach Using Elasticsearch

2017 ◽  
pp. 178-187
Author(s):  
Nikhil Chaudhari
Keyword(s):  
Data Analysis ◽  
Web Services ◽  
Open Source ◽  
Real Time ◽  
Service Oriented Architecture ◽  
Online Activity ◽  
Amazon Web Services ◽  
Service Oriented ◽  
Stream Analytics ◽  
Real Time Application

Elasticsearch has become an attractive open-source search and analytics engine for use cases such as log analytics, click stream analytics and real-time application monitoring. As a service, Elasticsearch is made available by Amazon Web services, Searchly.com, Bonsai and many other websites as a hosted engine. This hosted Elasticsearch service is known as Elastic Cloud. The aim of AWS (Amazon Web Services) is to provide Elasticsearch as a service to users. These web services can implement Service-oriented Architecture. In the following chapter Potential Reach is aggregated using the server. Potential Reach is a metric that indicates the reach of an online activity like tweet or comment. This number helps media marketers track the success of the brand or company.

DYNAMIC REST SERVICES ORCHESTRATION USING THE KNOWLEDGE BASE

2019 ◽  
Author(s):  
Kostyantyn Kharchenko
Keyword(s):  
Knowledge Base ◽  
Service Oriented Architecture ◽  
Main Idea ◽  
The Real ◽  
Server Side ◽  
Service Oriented ◽  
Services Orchestration ◽  
Client Side ◽  
Abstract Operation ◽  
Microservice Architecture

The approach to organizing the automated calculations’ execution process using the web services (in particular, REST-services) is reviewed. The given solution will simplify the procedure of introduction of the new functionality in applied systems built according to the service-oriented architecture and microservice architecture principles. The main idea of the proposed solution is in maximum division of the server-side logic development and the client-side logic, when clients are used to set the abstract computation goals without any dependencies to existing applied services. It is proposed to rely on the centralized scheme to organize the computations (named as orchestration) and to put to the knowledge base the set of rules used to build (in multiple steps) the concrete computational scenario from the abstract goal. It is proposed to include the computing task’s execution subsystem to the software architecture of the applied system. This subsystem is composed of the service which is processing the incoming requests for execution, the service registry and the orchestration service. The clients send requests to the execution subsystem without any references to the real-world services to be called. The service registry searches the knowledge base for the corresponding input request template, then the abstract operation description search for the request template is performed. Each abstract operation may already have its implementation in the form of workflow composed of invocations of the real applied services’ operations. In case of absence of the corresponding workflow in the database, this workflow implementation could be synthesized dynamically according to the input and output data and the functionality description of the abstract operation and registered applied services. The workflows are executed by the orchestrator service. Thus, adding some new functions to the client side can be possible without any changes at the server side. And vice versa, adding new services can impact the execution of the calculations without updating the clients.

Sign in / Sign up

Export Citation Format

Share Document