Refine
Document Type
- Article (7)
- Conference Proceeding (6)
Language
- English (13)
Has Fulltext
- yes (13)
Is part of the Bibliography
- no (13)
Keywords
- OSGi (3)
- CI/CD (2)
- Cloud Computing (2)
- DevOps (2)
- Versicherungsbetrieb (2)
- build automation (2)
- build server (2)
- API (1)
- Application Programming Interface (1)
- Auswahl (1)
- BaaS (Backend-as-a-service) (1)
- Big Data (1)
- Big Data Analytics (1)
- CEP (1)
- Continuous Delivery (1)
- Distributed file systems (1)
- Docker (1)
- ECA (1)
- EPN (1)
- Education (1)
- Event Admin (EA) (1)
- Event Processing Network (1)
- Event Processing Network Model (1)
- FaaS (Function-as-a-service) (1)
- Fault tolerance (1)
- Function as a Service (1)
- Hadoop (1)
- Istio (1)
- Kontinuierliche Integration (1)
- Kubernetes (1)
- LightSabre (1)
- MapReduce (1)
- MapReduce algorithm (1)
- Microservice (1)
- NoSQL databases. (1)
- Ontologies (1)
- OpenStack (1)
- PageRank (1)
- Pregel (1)
- REST <Informatik> (1)
- RESTful (1)
- Representational State Transfer (1)
- Richardson Maturity Model (1)
- RuleCore (1)
- SOA (1)
- Serverless Computing (1)
- Service Mesh (1)
- Shortest Path (1)
- Softwarewerkzeug (1)
- Verteiltes System (1)
- Word Counting (1)
- asynchronous messaging (1)
- cashing (1)
- cloud computing (1)
- complex event processing (CEP) (1)
- distributed environments (1)
- distributed systems (1)
- evaluation (1)
- events (1)
- large scale systems (1)
- load balancing (1)
- reliable message delivery (1)
- scaling (1)
- serverless architecture (1)
- serverless functions (1)
- service models (1)
- shopping cart system (1)
- tool evaluation (1)
- web services (1)
Institute
Hadoop is a Java-based open source programming framework, which supports the processing and storage of large volumes of data sets in a distributed computing environment. On the other hand, an overwhelming majority of organizations are moving their big data processing and storing to the cloud to take advantage of cost reduction – the cloud eliminates the need for investing heavily in infrastructures, which may or may not be used by organizations. This paper shows how organizations can alleviate some of the obstacles faced when trying to make Hadoop run in the cloud.
Our work is motivated primarily by the lack of standardization in the area of Event Processing Network (EPN) models. We identify general requirements for such models. These requirements encompass the possibility to describe events in the real world, to establish temporal and causal relationships among the events, to aggregate the events, to organize the events into a hierarchy, to categorize the events into simple or complex, to create an EPN model in an easy and simple way and to use that model ad hoc. As the major contribution, this paper applies the identified requirements to the RuleCore model.
In this paper, five ontologies are described, which include the event concepts. The paper provides an overview and comparison of existing event models. The main criteria for comparison are that there should be possibilities to model events with stretch in the time and location and participation of objects; however, there are other factors that should be taken into account as well. The paper also shows an example of using ontologies in complex event processing.
OSGi in Cloud Environments
(2013)
Heterogeneity has to be taken into account when integrating a set of existing information sources into a distributed information system that are nowadays often based on Service- Oriented Architectures (SOA). This is also particularly applicable to distributed services such as event monitoring, which are useful in the context of Event Driven Architectures (EDA) and Complex Event Processing (CEP). Web services deal with this heterogeneity at a technical level, also providing little support for event processing. Our central thesis is that such a fully generic solution cannot provide complete support for event monitoring; instead, source specific semantics such as certain event types or support for certain event monitoring techniques have to be taken into account. Our core result is the design of a configurable event monitoring (Web) service that allows us to trade genericity for the exploitation of source specific characteristics. It thus delivers results for the areas of SOA, Web services, CEP and EDA.
Nowadays, REST is the most dominant architectural style of choice at least for newly created web services. So called RESTfulness is thus really a catchword for web application, which aim to expose parts of their functionality as RESTful web services. But are those web services RESTful indeed? This paper examines the RESTfulness of ten popular RESTful APIs (including Twitter and PayPal). For this examination, the paper defines REST, its characteristics as well as its pros and cons. Furthermore, Richardson's Maturity Model is shown and utilized to analyse those selected APIs regarding their RESTfulness. As an example, a simple, RESTful web service is provided as well.
In this paper various techniques in relation to large-scale systems are presented. At first, explanation of large-scale systems and differences from traditional systems are given. Next, possible specifications and requirements on hardware and software are listed. Finally, examples of large-scale systems are presented.
OSGi is a popular Java-based platform, which has its roots in the area of embedded systems. However, nowadays it is used more and more in enterprise systems. To fit this new application area, OSGi has recently been extended with the Remote Services specification. This specification enables distribution, which OSGi was previously lacking. However, the specification provides means for synchronous communication only and leaves out asynchronous communication. As an attempt to fill a gap in this field, we propose, implement and evaluate an approach for the integration of asynchronous messaging into OSGi.
A Look at Service Meshes
(2021)
Service meshes can be seen as an infrastructure layer for microservice-based applications that are specifically suited for distributed application architectures. It is the goal to introduce the concept of service meshes and its use for microservices with the example of an open source service mesh called Istio. This paper gives an introduction into the service mesh concept and its relation to microservices. It also gives an overview of selected features provided by Istio as relevant to the above concept and provides a small sample setup that demonstrates the core features.