architectures part 2

service oriented architectures

building functional, scalable software systems from individual components which can interact with one another to perform tasks; modularity, reusability, and interoperability

object-based architectural styles

structuring a software system around components that encapsulate both data (the object's state) and behavior (the object's methods)

distributed or remote object

separation between interfaces and the objects implementing these interfaces allows us to place an interface at one machine, while the object itself resides on another machine

microservice architectural styles

many small and mutually independent programs can be easily composed to form larger programs, separate independent service, modularization

microservices

self-contained and capable of functioning autonomously; focuses on a specific domain or business capability

coarse-grained service composition

storage services are logically completely encapsulated into a single unit, of which an interface is made available to customers; composition of any services

representational state transfer

used in web services to allow applications to communicate over HTTP; single naming scheme, all services offer same interface, fully self-described, after execution forgets caller

put

modify a resource by transferring a new state

post

create a new resource

get

retrieve the state of a resource in

delete

delete a resource

resource-based service composition

services are designed to be modular, independent, and focused on specific_, interacting with other services to provide end-to-end solutions

publish-subscribe architecture

used in distributed systems for asynchronous communication between different components or services.

decoupled

enables the movement of messages between different components of the system without the components being aware of each other’s identity

publishers

components that create and send messages; do not send in a point-to-point manner

subscribers

components that receive and consume messages

channels or topics

a pub/sub message broker which groups messages into entities

loose coupling

system is more modular and flexible

high scalability

allows any number of publishers to communicate with any number of subscribers

language or protocol agnostic

straightforward to integrate into any tech stack

asynchronous event-driven communication

beneficial for low-latency apps