IIS Kapitel 6

Integrated Information Systems, Kapitel 6

Integrated Information Systems, Kapitel 6


D. B.
Diese Lernkarten behandeln Architektur- und Designmuster für Systeme auf Universitätsniveau. Sie konzentrieren sich auf verschiedene Architekturmuster wie Pipe and Filter, Client-Server, Model-View-Controller, Repository und Layered Architecture, sowie auf die Vorteile und Eigenschaften von Microservices. Die Karteikarten erklären auch die Typen von Design Patterns, ihre Elemente und die grundlegenden Konzepte hinter ihnen. Entwickler und Softwarearchitekten profitieren von diesen Lernkarten, da sie praktische Einblicke in bewährte Methoden für die Systemgestaltung bieten.
Cartes-fiches
12
Utilisateurs
1
Langue
Allemand
Catégorie
Informatique
Niveau
Université
Créé / Mis à jour
02.08.2016 / 03.08.2016

Cartes-fiches

Was sind Design Patterns?

  • A way of reusing abstract knowledge about a problem and its solution
  • Which is sufficientliy abstract to be reused in defferent settings
  • Description of the problem and the essence of its solution

Nenne die Pattern Elements

  • Name
  • Description
  • Problem description
  • Solution description
  • Consequences

Nenne die Typen von Design Patterns

  • Creational patterns: abstract the instantiation process
    • Abstract Factory: 
      • Provide an interface for creating families of related or dependent objects without specifying their concrete classes 
  • Structural patterns: are concerned with how objects form larger structures
    • Adapter:
      • Converts the interface of a class into another interface clients expect 
  • Behavioral patterns: are concerned with algorithms & responsibility
    • Observer 

Was sind Architectural Patterns?

A stylized description of good design practice, which has been tried and tested in different environments

Nenne 6 Architectural Patterns

  • Model-View-Controller (MVC)
  • Layerd Architecture
  • Repository Architecture
  • Client Server Architecture
  • Pipe and Filter Architecture
  • Peer-to-Peer

Layered Architecture Pattern

  • Organizes the system into layers with related functionality associated with each layer.
  • A layer provides features to the layer above it
  • models interfacing of sub-systems

Repository Architecture

  • All data in system is managed in a central repository that is accessible to all system components
  • Component don't interact with each other only though repository

Model-View-Controller

  • Seperates presentation and interaction from the system data
  • Three logical components that interact
    • Model: Core of the application, data and relevant methods 
    • View: Shows the state of the model 
    • Controller: Processes user commands and external events and triggers the adjustment of the model 

 

  • The view observes the model
  • The controller changes the model
  • Typically used for Web-interfaces and App-development 

Client-Server Architecture

  • Functionality of the system is organized into services
  • each service delivered form a seperate server
  • Clients are users of these services and access servers to make use of them

Pipe and Filter Architecture

  • processing is organized so that each processing component is discrete and carries out one type of data transformation
  • data flows from one component to another for processing

Was sind Microservices?

  • Small, autonomous services that work together#
  • Small: focused on doing on thing well
  • Autonomous: Seperate entity on a platform or own operating system process

 

Key Benefits of Microservices

  • Resilience
  • Scaling
  • Ease of deployment
  • Oraganizational alignment
  • Comosability
  • Replaceability

Étudier