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)
Der Bachelor-Studiengang Mediendesigninformatik der Hochschule Hannover ist ein Informatikstudiengang mit dem speziellen Anwendungsgebiet Mediendesign. In Abgrenzung von Studiengängen der Medieninformatik liegt der Anwendungsfokus auf der kreativen Gestaltung etwa von 3D-Modellierungen, Animationen und Computerspielen. Absolvent*innen des Studiengangs sollen an der Schnittstelle zwischen Informatik und Mediendesign agieren können, zum Beispiel bei der Erstellung von Benutzungsschnittstellen und VR/AR-Anwendungen. Der Artikel stellt das Curriculum des interdisziplinären Studiengangs vor und reflektiert nach dem Abschluss der ersten beiden Studierendenkohorten die Erfahrungen, indem die ursprünglichen Ziele den Zahlen der Hochschulstatistik und den Ergebnissen zweier Studierendenbefragungen gegenübergestellt werden.
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.
Microservices build a deeply distributed system. Although this offers significant flexibility for development teams and helps to find solutions for scalability or security questions, it also intensifies the drawbacks of a distributed system. This article offers a decision framework, which helps to increase the resiliency of microservices. A metamodel is used to represent services, resiliency patterns, and quality attributes. Furthermore, the general idea for a suggestion procedure is outlined.
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.
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.
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.
Microservices are meanwhile an established software engineering vehicle, which more and more companies are examining and adopting for their development work. Naturally, reference architectures based on microservices come into mind as a valuable thing to utilize. Initial results for such architectures are published in generic and in domain-specific form. Missing to the best of our knowledge however, is a domain-specific reference architecture based on microservices, which takes into account specifics of the insurance industry domain. Jointly with partners from the German insurance industry, we take initial steps to fill this gap in the present article. Thus, we aim towards a microservices-based reference software architecture for (at least German) insurance companies. As the main results of this article we thus provide an initial such reference architecture together with a deeper look into two important parts of it.
Even for the more traditional insurance industry, the Microservices Architecture (MSA) style plays an increasingly important role in provisioning insurance services. However, insurance businesses must operate legacy applications, enterprise software, and service-based applications in parallel for a more extended transition period. The ultimate goal of our ongoing research is to design a microservice reference architecture in cooperation with our industry partners from the insurance domain that provides an approach for the integration of applications from different architecture paradigms. In Germany, individual insurance services are classified as part of the critical infrastructure. Therefore, German insurance companies must comply with the Federal Office for Information Security requirements, which the Federal Supervisory Authority enforces. Additionally, insurance companies must comply with relevant laws, regulations, and standards as part of the business’s compliance requirements. Note: Since Germany is seen as relatively ’tough’ with respect to privacy and security demands, fullfilling those demands might well be suitable (if not even ’over-achieving’) for insurances in other countries as well. The question raises thus, of how insurance services can be secured in an application landscape shaped by the MSA style to comply with the architectural and security requirements depicted above. This article highlights the specific regulations, laws, and standards the insurance industry must comply with. We present initial architectural patterns to address authentication and authorization in an MSA tailored to the requirements of our insurance industry partners.
To avoid the shortcomings of traditional monolithic applications, the Microservices Architecture (MSA) style plays an increasingly important role in providing business services. This is true even for the more conventional insurance industry with its highly heterogeneous application landscape and sophisticated cross-domain business processes. Therefore, the question arises of how workflows can be implemented to grant the required flexibility and agility and, on the other hand, to exploit the potential of the MSA style. In this article, we present two different approaches – orchestration and choreography. Using an application scenario from the insurance domain, both concepts are discussed. We introduce a pattern that outlines the mapping of a workflow to a choreography.