Refine
Document Type
- Conference Proceeding (21) (remove)
Has Fulltext
- yes (21)
Is part of the Bibliography
- no (21)
Keywords
- Mikroservice (8)
- Serviceorientierte Architektur (7)
- Insurance Industry (5)
- Versicherungswirtschaft (5)
- SOA (4)
- Cloud Computing (3)
- Microservices (3)
- microservices (3)
- Big Data (2)
- Consistency (2)
- Microservice (2)
- Microservices Architecture (2)
- Rechnernetz (2)
- Urban Logistics (2)
- API (1)
- Adaptive IT Infrastructure (1)
- Angewandte Informatik (1)
- Application Programming Interface (1)
- Arbeitsablauf (1)
- Auswahl (1)
- Authentication (1)
- Authentifikation (1)
- Authorization (1)
- Autorisierung (1)
- BaaS (Backend-as-a-service) (1)
- Batteriefahrzeug (1)
- Battery Electric Vehicles (1)
- Big Data Analytics (1)
- CI/CD (1)
- Choreography (1)
- City-Logistik (1)
- Computersicherheit (1)
- Computersimulation (1)
- Curriculumentwicklung (1)
- Decision Support Tool (1)
- DevOps (1)
- Dienstgüte (1)
- Docker (1)
- Domain Driven Design (DDD) (1)
- EPN (1)
- Education (1)
- Elektromobilität (1)
- Entscheidungsunterstützungssystem (1)
- Event Processing Network (1)
- Event Processing Network Model (1)
- FaaS (Function-as-a-service) (1)
- Function as a Service (1)
- Hadoop (1)
- Indicator Measurement (1)
- Intelligentes Stromnetz (1)
- Interdiziplinäre Studiengänge (1)
- Istio (1)
- Kubernetes (1)
- MapReduce (1)
- Mediendesign (1)
- Mediendesignausbildung (1)
- Mediendesigninformatik (1)
- Mikro-Kraft-Wärme-Kopplung (1)
- Nachhaltigkeit (1)
- OpenStack (1)
- Orchestration (1)
- PageRank (1)
- Personennahverkehr (1)
- Portable Micro-CHP Unit (1)
- Praxisprojekte (1)
- Pregel (1)
- Programmierausbildung (1)
- Prüfstand (1)
- Quality of Service (1)
- REST <Informatik> (1)
- RESTful (1)
- Reference Architecture (1)
- Referenzmodell (1)
- Representational State Transfer (1)
- Resiliency (1)
- Richardson Maturity Model (1)
- RuleCore (1)
- SOA co-existence (1)
- Security (1)
- Serverless Computing (1)
- Service Mesh (1)
- Service Orientation (1)
- Service-orientation (1)
- Shortest Path (1)
- Simulation (1)
- Smart Grid (1)
- Software Architecture (1)
- Softwarearchitektur (1)
- Softwarewerkzeug (1)
- Test Bench (1)
- Versicherungsbetrieb (1)
- Verteiltes System (1)
- Virtuelles Laboratorium (1)
- Word Counting (1)
- Workflow (1)
- XML (1)
- XML-Model (1)
- XML-Schema (1)
- aerospace engineering (1)
- build automation (1)
- build server (1)
- data mapping (1)
- distributed systems (1)
- e-mobility (1)
- eduDScloud (1)
- generic interface (1)
- matrix calulations (1)
- pmCHP (1)
- private cloud (1)
- scaling (1)
- serverless architecture (1)
- serverless functions (1)
- service models (1)
- service-orientation (1)
- system integration (1)
- tool evaluation (1)
- virtual lab (1)
- workload decomposition (1)
Institute
- Fakultät IV - Wirtschaft und Informatik (21) (remove)
The transfer of historically grown monolithic software architectures into modern service-oriented architectures creates a lot of loose coupling points. This can lead to an unforeseen system behavior and can significantly impede those continuous modernization processes, since it is not clear where bottlenecks in a system arise. It is therefore necessary to monitor such modernization processes with an adaptive monitoring concept in order to be able to correctly record and interpret unpredictable system dynamics. For this purpose, a general measurement methodology and a specific implementation concept are presented in this work.
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.
The usage of microservices promises a lot of benefits concerning scalability and maintainability, rewriting large monoliths is however not always possible. Especially in scientific projects, pure microservice architectures are therefore not feasible in every project. We propose the utilization of microservice principles for the construction of microsimulations for urban transport. We present a prototypical architecture for the connection of MATSim and AnyLogic, two widely used simulation tools in the context of urban transport simulation. The proposed system combines the two tools into a singular tool supporting civil engineers in decision making on innovative urban transport concepts.
The automated transfer of flight logbook information from aircrafts into aircraft maintenance systems leads to reduced ground and maintenance time and is thus desirable from an economical point of view. Until recently, flight logbooks have not been managed electronically in aircrafts or at least the data transfer from aircraft to ground maintenance system has been executed manually. Latest aircraft types such as the Airbus A380 or the Boeing 787 do support an electronic logbook and thus make an automated transfer possible. A generic flight logbook transfer system must deal with different data formats on the input side – due to different aircraft makes and models – as well as different, distributed aircraft maintenance systems for different airlines as aircraft operators. This article contributes the concept and top level distributed system architecture of such a generic system for automated flight log data transfer. It has been developed within a joint industry and applied research project. The architecture has already been successfully evaluated in a prototypical implementation.
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.
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.
In microservice architectures, data is often hold redundantly to create an overall resilient system. Although the synchronization of this data proposes a significant challenge, not much research has been done on this topic yet. This paper shows four general approaches for assuring consistency among services and demonstrates how to identify the best solution for a given architecture. For this, a microservice architecture, which implements the functionality of a mainframe-based legacy system from the insurance industry, serves as an example.
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.
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 the context of modern mobility, topics such as smart-cities, Car2Car-Communication, extensive vehicle sensor-data, e-mobility and charging point management systems have to be considered. These topics of modern mobility often have in common that they are characterized by complex and extensive data situations. Vehicle position data, sensor data or vehicle communication data must be preprocessed, aggregated and analyzed. In many cases, the data is interdependent. For example, the vehicle position data of electric vehicles and surrounding charging points have a dependence on one another and characterize a competition situation between the vehicles. In the case of Car2Car-Communication, the positions of the vehicles must also be viewed in relation to each other. The data are dependent on each other and will influence the ability to establish a communication. This dependency can provoke very complex and large data situations, which can no longer be treated efficiently. With this work, a model is presented in order to be able to map such typical data situations with a strong dependency of the data among each other. Microservices can help reduce complexity.