This website uses cookies
We use cookies to continuously improve your experience on our site. More info.
Find and hire tech professionals
Dice backs GlossaryTech to keep it free for the community
Software Architecture | |
| A system that allows different software services to communicate by sending messages instead of talking directly. It is widely used in microservice architectures with tools such as RabbitMQ and Apache Kafka. | |
| A design approach where a backend service is built specifically for one user interface. It helps a front-end application get exactly the data it needs from a dedicated back-end through a tailored API. | |
| A specification that helps describe and document event-driven systems. It is commonly used alongside API designs to explain how services communicate using messages instead of direct requests. | |
| A pattern used to manage long-running processes across multiple services. It helps maintain consistency in Microservices systems without relying on a single transaction. | |
| A property where repeating the same operation produces the same result each time. It is especially important in API design and distributed systems. | |
| A specification used to describe and document API endpoints in a standard format. It allows tools to generate documentation, clients, and servers automatically. | |
| A tool that allows developers to build APIs without writing schemas or contracts separately. It is commonly used with ReactJS to enable type-safe communication. | |
| A design pattern that manages communication between different components. It helps reduce direct dependencies between objects. | |
| An infrastructure layer that manages communication between services. It is commonly used with Kubernetes in microservices architectures. | |
| A high-performance proxy used to manage service-to-service communication. It is a core component in many Service Mesh setups. | |
| A short document used to record important architectural decisions and the reasons behind them. It helps teams keep long term clarity in Software Architecture work and supports consistent Design Patterns. | |
| Jamstack is a modern web development architecture that stands for JavaScript, APIs, and Markup. It's not a specific technology, but rather a way of building websites and web applications that emphasizes decoupling the front end from the back end. Jamstack is popular for building websites, blogs, e-commerce sites, and web applications. It's particularly suitable for projects that require fast performance, high security, and low infrastructure complexity. | |
| An architectural pattern used in software design. It aims at creating loosely coupled application components that can be easily connected to their software environment by means of ports and adapters. | |
| Approach is an architecture that focuses on a separation of the functionality into many independent systems, making the complete logical system a collaboration of many smaller software systems. This avoids the problem of large monoliths that grow constantly and eventually become unmaintainable. | |
| Allows two systems to communicate with one another. An API essentially provides the language and contract for how two systems interact. Each API has documentation and specifications which determine how information can be transferred. | |
| A software architecture paradigm promoting the production, detection, consumption of, and reaction to events. | |
| Traditional unified model for the design of a software program. Monolithic software is designed to be self-contained; components of the program are interconnected and interdependent rather than loosely coupled as is the case with modular software programs. | |
| Remote Procedure Call (RPC) is a protocol that one program can use to request a service from a program located in another computer on a network without having to understand the network's details. | |
| A software paradigm based on the idea of disconnecting computational actors into stages (pipelines) that can execute concurrently. Dataflow can also be called stream processing or reactive programming. | |
| Application Programming Interface is the interface between the site and third-party programs and servers. On different online services or platforms, we can use the API to log in, instead of registering, through accounts in social networks. | |
| The Microsoft directory service for the Windows NT family. This service allows administrators to use group policies to ensure uniformity of user environment settings, software installation, updates, etc. | |
| Common responses to common problems that are largely ineffective and counterproductive. | |
| Observer, Iterator, Strategy, Factory, Singleton, Composite, Facade, Proxy, etc. | |
| A general repeatable solution to a commonly occurring problem in software design. It is a description or template for how to solve a problem that can be used in many different situations. | |
| Dependency Injection is a technique for achieving loose coupling between objects and their collaborators, or dependencies. DI is a method for writing better code. | |
