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
- Fakultät IV - Wirtschaft und Informatik (13) (remove)
In this paper we describe the selection of a modern build automation tool for an industry research partner of ours, namely an insurance company. Build automation has become increasingly important over the years. Today, build automation became one of the central concepts in topics such as cloud native development based on microservices and DevOps. Since more and more products for build automation have entered the market and existing tools have changed their functional scope, there is nowadays a large number of tools on the market that differ greatly in their functional scope. Based on requirements from our partner company, a build server analysis was conducted. This paper presents our analysis requirements, a detailed look at one of the examined tools and a summarized comparison of two tools.
In this paper we describe the selection of a modern build automation tool for an industry research partner of ours, namely an insurance company. Build automation has become increasingly important over the years. Today, build automation became one of the central concepts in topics such as cloud native development based on microservices and DevOps. Since more and more products for build automation have entered the market and existing tools have changed their functional scope, there is nowadays a large number of tools on the market that differ greatly in their functional scope. Based on requirements from our partner company, a build server analysis was conducted. This paper presents our analysis requirements, a detailed look at one of the examined tools and a summarizes our comparison of all three tools from our final comparison round.
Cloud Computing: Serverless
(2021)
A serverless architecture is a new approach to offering services over the Internet. It combines BaaS (Backend-as-a-service) and FaaS (Function-as-a-service). With the serverless architecture no own or rented infrastructures are needed anymore. In addition, the company does not have to worry about scaling any longer, as this happens automatically and immediately. Furthermore, there is no need any longer for maintenance work on the servers, as this is completely taken over by the provider. Administrators are also no longer needed for the same reason. Finally, many ready-made functions are offered, with which the development effort can be reduced. As a result, the serverless architecture is very well suited to many application scenarios, and it can save considerable costs (server costs, maintenance costs, personnel costs, electricity costs, etc.). The company only must subdivide the source code of the application and upload it to the provider’s server. The rest is done by the provider.
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.
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.
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.
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.
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.
OSGi in Cloud Environments
(2013)