USM uses the term workflow pattern - in its own way.

There are many ways people use the concept of 'patterns'. On this page, we list a few.

A pattern language for microservices - The beginnings of a pattern language for microservice architectures, describing:

  • Core patterns
  • Monolithic architecture
  • Microservices architecture
  • API gateway
  • Deployment patterns
  • Multiple service instances per host
  • Service instance per host
  • Service instance per VM
  • Service instance per Container
  • Service discovery
  • Client-side discovery
  • Server-side discovery
  • Service registry
  • Self registration
  • 3rd party registration
  • Data
  • Database per Service

Business rules versus busines requirements - Gladys S.W. Lam - a Principal at BRSolutions.com - explains in very clear terms the differences between Business Rules and Business Requirements.http://www.brcommunity.com/lam.php

CloudPatterns.org - CloudPatterns.org is a community site dedicated to documenting a master patterns catalog comprised of design patterns that capture and modularize technology-centric solutions distinct or relevant to modern-day cloud computing platforms and business-centric cloud technology architectures.
Part of this catalog is comprised of compound patterns that tackle contemporary cloud delivery and deployment models (such as public cloud, IaaS, etc.) and decompose them into sets of co-existent patterns that establish core and optional feature sets provided by these environments.
Cloud computing patterns are applied via the implementation of individual or combinations of different technology mechanisms. Together, the documentation of patterns and mechanisms provides an extremely concrete view of cloud architecture layers and the individual building blocks that represent the moving parts that can be assembled in creative ways to leverage cloud environments for business automation. Each design pattern in the cloud computing catalog is associated with one or more mechanisms.
To further learn about design patterns, compound patterns, and mechanisms, visit these overview pages.

Here is a summary of how design patterns, compound patterns, and mechanisms related to each other:

  • Mechanisms represent technology artifacts that can be combined to form cloud technology architectures.
  • Design patterns represent proven solutions to common problems.
  • Cloud computing design patterns are (partially or entirely) applied by implementing different combinations of cloud computing mechanisms.
  • Compound patterns are comprised of specific combinations of core (required) and extension (optional) member patterns.

D-NET LAB service design patterns - D-NET supports a component-oriented programming methodology where services can be designed assuming the existence of given type of services, even though instances of such resource might not be yet available (i.e. registered) to the infrastructure or their location is unknown at the time of realizing the service. D-NET services are thus designed to discover the resources they need at run-time, and possibly react to their absence. D-NET services are designed according to one or more of the following patterns: user operated service, functionality service, factory service, manager service. Read more....

Data cleansing pattern - Information service patterns, Part 3: Data cleansing pattern, IBM, 2007.
The data cleansing pattern specifies rules for data standardization, matching, and survivorship that enforce consistency and quality on the data it is applied against. The data cleansing pattern validates the data (whether persistent or transient) against the cleansing rules and then applies changes to enforce consistency and quality. In this article, you learn to apply the data cleansing pattern within a Service-Oriented Architecture (SOA) context. This pattern specification helps you, as a data or application architect, to make informed architectural decisions and to improve decision guidelines. Read it here....

Data consolidation pattern - Information service patterns, Part 2: Data consolidation patter, IBM, 2006.
The data consolidation pattern specification helps data and application architects make informed architectural decisions and improve decision guidelines. In this article you will see how you can apply the pattern in the SOA context. The primary business driver for the data consolidation pattern, also referred to as the data population pattern, is to gather and reconcile data from multiple data sources before this information is needed. To do so, it extracts data from one or more sources, transforms that data into the desired target format, and loads it into some persistent data target. The prepopulation of a persistent target is a key differentiator between this pattern and the data federation pattern covered in Part 1 of this series. Read it here....

Data federation pattern - Information service patterns, Part 1: Data federation pattern. IBM, 2012.
The data federation pattern virtualizes data from multiple disparate information sources. The pattern creates an integrated view into distributed information without creating data redundancy while federating both structured and unstructured information. This article describes the federation of structured information (data) with a focus on the SOA context. This pattern specification helps data and application architects make informed decisions on data architecture and document decision guidelines. Read it here.....

Design Patterns for Information in a Service-Oriented Architecture- An article about design patterns for information management techniques that improve the information services used by your organization. It describes a pattern language called the Patterns of Information Management (PoIM). PoIM contains over 200 linked design patterns that use consistent terminology and concepts, resulting in a body of work that can be used at all levels, from the enterprise architect down to the individual project.
An example design pattern for an enterprise service bus (ESB) is used to illustrate the structure of a design pattern and how such a pattern links to other PoIM patterns to create a pattern language.
Published: October 24, 2013 • Service Technology Magazine Issue LXXVII. Read it here.....

Gov.UK Design patterns - These patterns are based on the research and experience of the whole GOV.UK design community. If you can’t find the pattern you’re looking for here, we’re discussing many more on designpatterns.hackpad.com.

Master Data Management architecture patterns - Information service patterns, Part 4: Master Data Management architecture pattern. A pattern taxonomy, IBM, 2007
Master Data Management (MDM) brings you a methodology for maintaining consistent data across diverse business functions. This article describes the taxonomy of Enterprise MDM-related architecture patterns. After an initial introduction of terminology and pattern concepts, you'll learn about the MDM methods of use: collaborative MDM, operational MDM, and analytical MDM. Explore the most important attributes and types of MDM architecture patterns, focusing on patterns, such as MDM application integration, MDM information integration, and MDM enterprise system deployment patterns. The relationship between MDM architecture patterns and the methods of use of Enterprise MDM systems is discussed as well. Finally, you'll learn how to use these architecture patterns to compose comprehensive MDM architecture and solution blueprints. Read it here....

Patterns: Service-Oriented Architecture ... - IBM redbook: Patterns: Service-Oriented Architecture and Web Services . An IBM paper on the patterns for e-business: here. April 2004.

The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying Web applications. This IBM® Redbook focuses how the Self-Service and Extended Enterprise business patterns, and the Application Integration pattern, can be used to start implementing solutions using the service-oriented architecture approach.
It guides you through the process of selecting and applying Business, Application and Runtime patterns. Next, the platform-specific Product mappings are identified based upon the selected Runtime pattern.
The book presents guidelines for applying the Patterns and service-oriented architecture approach to a sample business scenario and for selecting Web services technologies.
It provides detailed design, development, and runtime guidelines for several scenarios, including synchronous and asynchronous service buses, UDDI service directory, and the Web Services Gateway.
The book concludes with an examination of how a service-oriented architecture can provide a step in the direction of IBM’s e-business on-demand vision.

Service Design Patterns - This site site provides a quick overview of several design patterns from the book that address these questions. The patterns you will find here may be used to create web services that either leverage SOAP/ WSDL or follow the REST architectural style.

Service Interaction Patterns - Article on some micro-patterns in service interaction models.http://www.workflowpatterns.com/documentation/documents/serviceinteraction_BPM05...

Service Patterns and Anti-Patterns - Principles of Service Design: Service Patterns and Anti-Patterns. The Principles of Service Design series has been developed to communicate best practices and sample codes when relevant. The first in this multi-paper series, this paper provides fundamental principles for designing and implementing Web services, including a brief review of Service Oriented Architecture (SOA) concepts and a detailed discussion of several patterns and anti-patterns that developers can leverage when building Web services. Guidance is applicable to any programming language or platform for which Web services can be developed and deployed. (18 printed pages) https://msdn.microsoft.com/en-us/library/ms954638.aspx

Seven Microservices Anti-patterns - Buzzwords often give context to concepts that evolved and needed a good “tag” to facilitate dialogue. Microservices is a new “tag” that defines areas I have personally been discovering and using for some time now.  Articles and conferences described something that I slowly realized I had been evolving in my own personal experience for the past few years. Read the article...

Terminology IS versus IT - Result of a global poll on the question "Does IS contain IT or does IT contain IS", where IT = information technology and IS = information system. IS-contains-IT

TOGAF and patterns - A "pattern" has been defined as: "an idea that has been useful in one practical context and will probably be useful in others" [Analysis Patterns - Reusable Object Models].
In TOGAF, patterns are considered to be a way of putting building blocks into context; for example, to describe a re-usable solution to a problem. Building blocks are what you use: patterns can tell you how you use them, when, why, and what trade-offs you have to make in doing so. Read more....

Wikipedia page on patterns - A pattern, apart from the term's use to mean "Template", is a discernible regularity in the world or in a manmade design. As such, the elements of a pattern repeat in a predictable manner. A geometric pattern is a kind of pattern formed of geometric shapes and typically repeating like a wallpaper. Read it here....

Workflow patterns - The Workflow Patterns initiative is a joint effort of Eindhoven University of Technology (led by Professor Wil van der Aalst) and Queensland University of Technology (led by Professor Arthur ter Hofstede) which started in 1999. The aim of this initiative is to provide a conceptual basis for process technology. In particular, the research provides a thorough examination of the various perspectives (control flow, data, resource, and exception handling) that need to be supported by a workflow language or a business process modelling language. The results can be used for examining the suitability of a particular process language or workflow system for a particular project, assessing relative strengths and weaknesses of various approaches to process specification, implementing certain business requirements in a particular process-aware information system, and as a basis for language and tool development.
On this web site you will find detailed descriptions of patterns for the various perspectives relevant for process-aware information systems: control-flow, data, resource, and exception handling. In addition you will find detailed evaluations of various process languages, (proposed) standards for web service compositions, and workflow systems in terms of this patterns.
We encourage interactions with interested parties about this research and its applications. For example, vendors can provide self-assessments of evaluations of their products (see the Vendors Corner). Also, we appreciate any feedback in relation to our evaluations (e.g. errors or inaccuracies).