Refine
Year of publication
Document Type
- Conference Proceeding (20)
- Article (9)
Language
- English (29) (remove)
Has Fulltext
- yes (29)
Is part of the Bibliography
- no (29)
Keywords
- Mikroservice (8)
- Serviceorientierte Architektur (8)
- SOA (7)
- Insurance Industry (5)
- Versicherungswirtschaft (5)
- Cloud Computing (3)
- Microservices (3)
- OSGi (3)
- microservices (3)
- Big Data (2)
- CEP (2)
- CI/CD (2)
- Consistency (2)
- DevOps (2)
- Dienstgüte (2)
- ECA (2)
- Indicator Measurement (2)
- Microservice (2)
- Microservices Architecture (2)
- Rechnernetz (2)
- Service-orientation (2)
- Urban Logistics (2)
- Versicherungsbetrieb (2)
- XML-Model (2)
- XML-Schema (2)
- build automation (2)
- build server (2)
- API (1)
- Adaptive IT Infrastructure (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)
- Choreography (1)
- City-Logistik (1)
- Complex Event Processing (CEP) (1)
- Computersicherheit (1)
- Computersimulation (1)
- Continuous Delivery (1)
- Decision Support Tool (1)
- Distributed file systems (1)
- Docker (1)
- Domain Driven Design (DDD) (1)
- EPN (1)
- Education (1)
- Elektromobilität (1)
- Entscheidungsunterstützungssystem (1)
- Event Admin (EA) (1)
- Event Processing Network (1)
- Event Processing Network Model (1)
- Event monitoring (1)
- FaaS (Function-as-a-service) (1)
- Fault tolerance (1)
- Function as a Service (1)
- Hadoop (1)
- Intelligentes Stromnetz (1)
- Istio (1)
- Kontinuierliche Integration (1)
- Kubernetes (1)
- LightSabre (1)
- MapReduce (1)
- MapReduce algorithm (1)
- Mikro-Kraft-Wärme-Kopplung (1)
- Nachhaltigkeit (1)
- NoSQL databases. (1)
- Ontologies (1)
- OpenStack (1)
- Orchestration (1)
- PageRank (1)
- Personennahverkehr (1)
- Portable Micro-CHP Unit (1)
- Pregel (1)
- Prüfstand (1)
- Quality of Service (1)
- Quality of Service (QoS) (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)
- Shortest Path (1)
- Simulation (1)
- Smart Grid (1)
- Software Architecture (1)
- Softwarearchitektur (1)
- Softwarewerkzeug (1)
- Test Bench (1)
- Verteiltes System (1)
- Virtuelles Laboratorium (1)
- Web services (1)
- Word Counting (1)
- Workflow (1)
- XML (1)
- aerospace engineering (1)
- asynchronous messaging (1)
- cashing (1)
- cloud computing (1)
- complex event processing (CEP) (1)
- data mapping (1)
- distributed environments (1)
- distributed systems (1)
- e-mobility (1)
- eduDScloud (1)
- evaluation (1)
- events (1)
- generic interface (1)
- large scale systems (1)
- load balancing (1)
- matrix calulations (1)
- pmCHP (1)
- private cloud (1)
- reliable message delivery (1)
- scaling (1)
- serverless architecture (1)
- serverless functions (1)
- service models (1)
- service-orientation (1)
- shopping cart system (1)
- system integration (1)
- tool evaluation (1)
- virtual lab (1)
- web services (1)
- workload decomposition (1)
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.
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.
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.
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 the workflow of the project 'Untersuchungs-, Simulations- und Evaluationstool für Urbane Logistik` (USEfUL) is presented. Aiming to create a web-based decision support tool for urban logistics, the project needed to integrate multiple steps into a single workflow, which in turn needed to be executed multiple times. While a service-oriented system could not be created, the principles of service orientation was utilized to increase workflow efficiency and flexibility, allowing the workflow to be easily adapted to new concepts or research areas.
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.
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.
Microservices is an architectural style for complex application systems, promising some crucial benefits, e.g. better maintainability, flexible scalability, and fault tolerance. For this reason microservices has attracted attention in the software development departments of different industry sectors, such as ecommerce and streaming services. On the other hand, businesses have to face great challenges, which hamper the adoption of the architectural style. For instance, data are often persisted redundantly to provide fault tolerance. But the synchronization of those data for the sake of consistency is a major challenge. Our paper presents a case study from the insurance industry which focusses consistency issues when migrating a monolithic core application towards microservices. Based on the Domain Driven Design (DDD) methodology, we derive bounded contexts and a set of microservices assigned to these contexts. We discuss four different approaches to ensure consistency and propose a best practice to identify the most appropriate approach for a given scenario. Design and implementation details and compliance issues are presented as well.