Programming
Software development: programming languages, coding, libraries and frameworks, software engineering and architecture, source control, developer tools, databases, and infrastructure.
-
Version Identification patterns.arcitura.com
Identifies the version of a service.
-
Service Refactoring patterns.arcitura.com
Refactors a service to improve its design and performance.
-
Service Decomposition patterns.arcitura.com
Breaks down a monolithic service into smaller, more manageable pieces.
-
Redundant Implementation patterns.arcitura.com
Implements multiple versions of a service for improved flexibility.
-
Microservice Deployment patterns.arcitura.com
Deploys services as independent, autonomous units for improved scalability and resilience.
-
Functional Decomposition patterns.arcitura.com
Breaks down services into smaller, more manageable components.
-
Canonical Versioning patterns.arcitura.com
Defines a standard versioning scheme for inventory resources.
-
Oracle SOA Suite oracle.com
Comprehensive SOA platform that orchestrates services into composite applications, driving efficient business process integration.
-
Oracle GoldenGate oracle.com
Enterprise-grade real-time data integration and replication solution that provides comprehensive CDC capabilities for heterogeneous databases and cloud platforms.
-
Oracle AQ oracle.com
Integrated messaging solution within Oracle databases, offering reliable and efficient message delivery.
-
Open Banking openbanking.org.uk
UK standard defining secure APIs that enable banks to share account and payment data with authorized third-party providers.
-
Anypoint Platform mulesoft.com
Combines API management and integration into one platform, enabling seamless connectivity across diverse applications.
-
Anypoint Platform mulesoft.com
Combines API design, integration, and management into one unified platform, streamlining connectivity and development.
-
Error Report microservice-api-patterns.org
How can an API provider inform its clients about communication and processing faults? How can this information be made independent of the underlying communication technologies and platforms (for example, protocol-level headers representing status codes)?
-
Context Representation microservice-api-patterns.org
How can API consumers and providers exchange context information without relying on any particular remoting protocols? How can identity information and quality properties in a request be made visible to related subsequent ones in conversations?
-
API Key microservice-api-patterns.org
How can an API provider identify and authenticate clients and their requests?
-
Parameter Forest microservice-api-patterns.org
How can multiple Parameter Trees be exposed as request or response payload of an API operation?
-
Atomic Parameter List microservice-api-patterns.org
How can multiple related Atomic Parameters be combined in a representation element so that each of them stays simple, but their relatedness becomes explicit in the API Description and the runtime message exchanges?
-
Atomic Parameter microservice-api-patterns.org
How can simple, unstructured data (such as a number, a string, a Boolean value, or a block of binary data) be exchanged between API client and API provider?
-
Link Element microservice-api-patterns.org
How can API endpoints and operations be referenced in request and response message payloads so that they can be called remotely?
-
Id Element microservice-api-patterns.org
How can API elements be distinguished from each other at design time and at runtime? When applying domain-driven design, how can elements of the Published Language be identified?
-
Data Element microservice-api-patterns.org
How can domain/application-level information be exchanged between API clients and API providers without exposing provider-internal data definitions in the API? How can API client and API provider be decoupled from a data management point of view?
-
State Transition Operation microservice-api-patterns.org
How can a client initiate a processing action that causes the provider-side application state to change? How can API clients and API providers share the responsibilities required to execute and control business processes and their activities?
-
State Creation Operation microservice-api-patterns.org
How can an API provider allow its clients to report that something has happened that the provider needs to know about, for instance, to trigger instant or later processing?
-
Retrieval Operation microservice-api-patterns.org
How can information available from a remote party (the API provider, that is) be retrieved to satisfy an information need of an end user or to allow further client-side processing?
-
Reference Data Holder microservice-api-patterns.org
How should data that is referenced in many places, lives long, and is immutable for clients be treated in API endpoints? How can such reference data be used in requests to and responses from Processing Resources or Information Holder Resources?
-
Operational Data Holder microservice-api-patterns.org
How can an API support clients that want to create, read, update, and/or delete instances of domain entities that represent operational data: data that is rather short-lived, changes often during daily business operations, and has many outgoing relations?
-
Master Data Holder microservice-api-patterns.org
How can I design an API that provides access to master data that lives for a long time, does not change frequently, and will be referenced from many clients?
-
Link Lookup Resource microservice-api-patterns.org
How can message representations refer to other, possibly many and frequently changing, API endpoints and operations without binding the message recipient to the actual addresses of these endpoints?
-
Processing Resource microservice-api-patterns.org
How can an API provider allow its clients to trigger an action in it?
-
Information Holder Resource microservice-api-patterns.org
How can domain data be exposed in an API, but its implementation still be hidden? How can an API expose data entities so that API clients can access and/or modify these entities concurrently without compromising data integrity and quality?
-
Linked Information Holder microservice-api-patterns.org
How can messages be kept small even when an API deals with multiple information elements that reference each other?
-
Service Level Agreement microservice-api-patterns.org
How can an API client learn about the specific quality-of-service characteristics of an API and its endpoint operations? How can these characteristics, and the consequences of not meeting them, be defined and communicated in a measurable way?
-
Rate Limit microservice-api-patterns.org
How can the API provider prevent API clients from excessive API usage?
-
Pricing Plan microservice-api-patterns.org
How can the API provider meter API service consumption and charge for it?
-
Wish Template microservice-api-patterns.org
How can an API client inform the API provider about nested data that it is interested in? How can such preferences be expressed flexibly and dynamically?
-
Wish List microservice-api-patterns.org
How can an API client inform the API provider at runtime about the data it is interested in?
-
Pagination microservice-api-patterns.org
How can an API provider deliver large sequences of structured data without overwhelming clients?
-
Conditional Request microservice-api-patterns.org
How can unnecessary server-side processing and bandwidth usage be avoided when frequently invoking API operations that return rarely changing data?
-
Solution-Internal API microservice-api-patterns.org
How can access to and usage of an API be limited to an application, for instance, components in the same or another logical layer and/or physical tier?
-
Public API microservice-api-patterns.org
How can an API be made available to an unlimited and/or unknown number of API clients outside the organization that are globally, nationally, and/or regionally distributed?
-
Frontend Integration microservice-api-patterns.org
How can client-side end-user interfaces that are physically separated from server-side business logic and data storage be populated and updated with computing results, result sets from searches in data sources, and detailed information about data entities? How can application…
-
Community API microservice-api-patterns.org
How can the visibility of and the access to an API be restricted to a closed user group that does not work for a single organizational unit but for multiple legal entities (such as companies, nonprofit/nongovernment organizations, and governments)?
-
Backend Integration microservice-api-patterns.org
How can distributed applications and their parts, which have been built independently and are deployed separately, exchange data and trigger mutual activity while preserving system-internal conceptual integrity without introducing undesired coupling?
-
API Description microservice-api-patterns.org
Which knowledge should be shared between an API provider and its clients? How should this knowledge be documented?
-
Version Identifier microservice-api-patterns.org
How can an API provider indicate its current capabilities as well as the existence of possibly incompatible changes to clients in order to prevent malfunctioning of clients due to undiscovered interpretation errors?
-
Two In Production microservice-api-patterns.org
How can a provider gradually update an API without breaking existing clients but also without having to maintain a large number of API versions in production?
-
Semantic Versioning microservice-api-patterns.org
How can stakeholders compare API versions to detect immediately whether they are compatible?
-
Limited Lifetime Guarantee microservice-api-patterns.org
How can a provider let clients know for how long they can rely on the published version of an API?
-
Experimental Preview microservice-api-patterns.org
How can providers make the introduction of a new API, or new API version, less risky for their clients and obtain early adopter feedback without having to freeze the API design prematurely?
- next page of items loading…
