Module 1 Part 2

Architectural Styles

Different ways to transition from layered software architecture to tiered architecture running on physical systems, supporting specific characteristics and organizational needs.

Microservices Architecture

An emerging architecture where small autonomous services communicate via APIs, each responsible for a single business capability and managing its own data.

Orchestration

Automated configuration management and coordination of computer systems, applications, and services, crucial for managing the complexity of a microservices-based architecture.

Microservices

Small, less complex services that implement a single business function and can be implemented by different teams.

Big Computer Architecture

Splits work across parallel tasks, suitable for parallelizable workloads, and offloads tightly coupled tasks to different processing engines.

Big Data Architecture

Handles large volumes of data, processes and analyzes data, and is used for storing and processing unstructured data.

Reliability

Designing applications to recover from failures and continue functioning, often achieved through redundancy and self-healing mechanisms.

Scalability

The ability of an application to grow with demand, ensuring systems can handle peak loads and increased user activity.

Evolutionary Architecture

Systems designed to evolve over time, allowing businesses to take advantage of new innovations and technologies.

Redundancy

Building additional copies of applications to avoid total failure and ensure continuous operation in case of failures.

Self-healing

Applications that can automatically recover from failures without human intervention, ensuring continuous operation.

Active-Passive Database Servers

Database setup where one server actively handles requests while the other copies data and takes over if the active server fails.

Heartbeat Signal

Monitoring mechanism between servers to ensure they are alive and functioning, used to trigger failover in case of server failures.

Redundancy

Planning for scenarios with multiple levels of backup systems to avoid single points of failure and ensure reliability.

Scaling out

Increasing processing capacity by adding more systems to the IT infrastructure.

Scaling up

Enhancing system power and capability by adding more resources like RAM, storage, and processing.

Availability zones

Geographically dispersed data centers to ensure system availability and reliability in case of natural disasters.

Role-based security

Designing applications with multiple roles for users, each assigned specific rights and privileges within the database.

Evolution in design

Adapting applications over time by using highly cohesive but loosely coupled services to facilitate changes without disrupting the entire system.

Microservices architecture

Utilizing decoupled autonomous services that implement a single business capability for flexibility and scalability.

Open interfaces

Exposing well-defined APIs with structured contracts for interacting with services and managing API evolution and version control.

Integration and interoperability

Ensuring different systems from various vendors can work together and share data effectively to perform tasks as intended.

API

A set of features and rules that act as an interface between an application or service offering services and other entities, such as software or hardware.

Private API

APIs designed for internal use by a company, maintaining complete control over the API and connecting only to designated systems.

Public API

Open to anyone following Internet protocol, allowing third parties to develop applications interacting with the API.

Partner API

Shared with specific business partners, potentially monetized, and used for specific collaborations.

Message Brokers

Inter-application communication technology facilitating a common integration mechanism, managing communications between on-premises systems and cloud components.

Middleware

Software layer translating and enabling communication between incompatible systems, hiding differences between applications and underlying components.

DCE

Common Object Request Broker Architecture, a middleware standard for connecting systems.

ODBC

Open Database Connectivity, middleware used for connecting to databases.

Fusion Middleware

Oracle's integration layer connecting different applications into a unified enterprise system.

SAP Hana

SAP's primary application without a middleware layer, built up from the ground by the same company.