Microservices - Revision history

User at 18:39, 30 August 2023

2023-08-30T18:39:32Z

User at 00:20, 25 August 2023

2023-08-25T00:20:09Z

User at 00:19, 25 August 2023

2023-08-25T00:19:05Z

User at 00:17, 25 August 2023

2023-08-25T00:17:28Z

User at 11:34, 8 July 2021

2021-07-08T11:34:06Z

User at 22:02, 29 June 2021

2021-06-29T22:02:08Z

User at 22:00, 29 June 2021

2021-06-29T22:00:11Z

User at 21:55, 29 June 2021

2021-06-29T21:55:37Z

User at 21:38, 29 June 2021

2021-06-29T21:38:40Z

User: Created page with "== Definition of MicroservicesWhat are Microservices? [https://microservices.io/ Microservices.io] == '''Microservices''' - also known as the '''microservice archit..."

2021-06-29T21:25:05Z

Created page with "== Definition of Microservices<ref>What are Microservices? [https://microservices.io/ Microservices.io]</ref> == '''Microservices''' - also known as the '''microservice archit..."

New page

== Definition of Microservices<ref>What are Microservices? [https://microservices.io/ Microservices.io]</ref> ==
'''Microservices''' - also known as the '''microservice architecture''' - is an [[Architectural Style|architectural style]] that structures an [[Application}application]] as a collection of [[Service|services]] that are:
*Highly maintainable and testable
*Loosely coupled
*Independently deployable
*Organized around [[Business Capability|business capabilities]]
*Owned by a small team
The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an [[Organization|organization]] to evolve its [[Technology|technology]] stack.

[[File:File.png|200px|thumb|left|alt text]]<br />
source: [https://dzone.com/articles/what-are-microservices-actually DZone]

The microservice architecture is not a silver bullet. It has several drawbacks. Moreover, when using this [[Architecture|architecture]] there are numerous issues that you must address. The microservice [[Architectural Pattern|architecture pattern]] language is a collection of patterns for applying the microservice architecture. It has two goals:
*The pattern language enables you to decide whether microservices are a good fit for your application.
*The pattern language enables you to use the microservice architecture successfully.
A good starting point is the Monolithic Architecture pattern, which is the traditional architectural style that is still a good choice for many applications. It does, however, have numerous limitations and issues and so a better choice for large/complex applications is the Microservice architecture pattern.

=== What Microservices are Not<ref>What Microservices are Not [https://www.ibm.com/cloud/learn/microservices IBM]</ref> ===
Microservices might also be understood by what they are not. The two comparisons drawn most frequently with microservices architecture are monolithic architecture and [[Service Oriented Architecture (SOA)|service-oriented architecture (SOA)]].

The difference between microservices and monolithic architecture is that microservices compose a single application from many smaller, loosely coupled services as opposed to the monolithic approach of a large, tightly coupled application

The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)}enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.

@@ Line 47: / Line 47: @@
 == Microservices Use Cases<ref>Example Use Cases for Microservices [https://hazelcast.com/glossary/microservices/ Hazelcast]</ref> ==
-Many use cases are applicable for microservices, especially those that involve an extensive data pipeline. For example, a microservices-based system would be ideal for a reporting system on a company’s retail store sales. Each step in the data preparation process would be handled by a microservice: [[Data Collection|data collection]], [[Data Cleansing}cleansing]], normalization, enrichment, aggregation, reporting, etc. The [[Workflow|workflow]] naturally creates a trackable lineage so if any problems are encountered in the data, it is relatively easy to trace back which microservice might need to be updated.
+Many use cases are applicable for microservices, especially those that involve an extensive data pipeline. For example, a microservices-based system would be ideal for a reporting system on a company’s retail store sales. Each step in the data preparation process would be handled by a microservice: [[Data Collection|data collection]], [[Data Cleansing|cleansing]], normalization, enrichment, aggregation, reporting, etc. The [[Workflow|workflow]] naturally creates a trackable lineage so if any problems are encountered in the data, it is relatively easy to trace back which microservice might need to be updated.
 Another use case entails [[Machine Learning|machine learning (ML)]]. A microservices-based ML environment collects, aggregates, and analyzes a data flow so that the ML framework can determine an outcome. In such an environment, the data runs through a workflow that has many steps, and each step is handled by a microservice. One advantage of using a microservices architecture for machine learning is that multiple machine learning frameworks can be included in the workflow so that multiple models can be created on the same data flow. This is useful when the machine learning frameworks are targeting a predicted outcome, and having multiple frameworks running simultaneously provides a comparison around which model is providing the best results.

@@ Line 13: / Line 13: @@
-The microservice architecture is not a silver bullet. It has several drawbacks. Moreover, when using this [[Architecture|architecture]] there are numerous issues that you must address. The microservice [[Architectural Pattern|architecture pattern]] language is a collection of patterns for applying the microservice architecture. It has two goals:
+The microservice architecture is not a silver bullet. It has several drawbacks. Moreover, when using this architecture there are numerous issues that you must address. The microservice [[Architectural Pattern|architecture pattern]] language is a collection of patterns for applying the microservice architecture. It has two goals:
 *The pattern language enables you to decide whether microservices are a good fit for your application.
 *The pattern language enables you to use the microservice architecture successfully.
@@ Line 95: / Line 95: @@
 #[[Client Server Architecture]]
 #[[Architectural Principles]]
 #[[Serverless Architecture]]
 #[[Enterprise Architecture]]
 #[[Service Oriented Architecture (SOA)]]

@@ Line 93: / Line 93: @@
 == See Also ==
-[[Client Server Architecture]]<br />
+#[[Client Server Architecture]]
-[[Architecture]]<br />
+#[[Architectural Principles]]
-[[Architectural Principles]]<br />
+#[[Architectural Pattern]]
-[[Architectural Pattern]]<br />
+#[[Serverless Architecture]]
-[[Architectural Risk]]<br />
+#[[Architectural Style]]
-[[Architectural Style]]<br />
+#[[Enterprise Architecture]]
-[[Enterprise Architecture]]<br />
+#[[Service Oriented Architecture (SOA)]]
-[[Service Oriented Architecture (SOA)]]<br />
+#[[Distributed Computing]]
-[[IT Governance]]<br />
 == References ==
 <references/>

@@ Line 93: / Line 93: @@
 == See Also ==
 [[Architecture]]<br />
 [[Architectural Principles]]<br />

← Older revision		Revision as of 22:02, 29 June 2021
Line 25:		Line 25:

	The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)\|enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.		The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)\|enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.
		+
		+
		+	__TOC__

@@ Line 6: / Line 6: @@
 *Organized around [[Business Capability|business capabilities]]
 *Owned by a small team
-The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an [[Organization|organization]] to evolve its [[Technology|technology]] stack.
+The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an [[Organization|organization]] to evolve its technology stack.

← Older revision		Revision as of 22:00, 29 June 2021
Line 87:		Line 87:
	*Debugging: Remote debugging through your local integrated development environment (IDE) isn’t an option and it won’t work across dozens or hundreds of services. Unfortunately there’s no single answer to how to debug at this time.		*Debugging: Remote debugging through your local integrated development environment (IDE) isn’t an option and it won’t work across dozens or hundreds of services. Unfortunately there’s no single answer to how to debug at this time.
	*Connectivity: Consider service discovery, whether centralized or integrated.		*Connectivity: Consider service discovery, whether centralized or integrated.
		+
		+
		+	== See Also ==
		+	[[Architecture]]<br />
		+	[[Architectural Principles]]<br />
		+	[[Architectural Pattern]]<br />
		+	[[Architectural Risk]]<br />
		+	[[Architectural Style]]<br />
		+	[[Enterprise Architecture]]<br />
		+	[[Service Oriented Architecture (SOA)]]<br />
		+	[[IT Governance]]<br />
		+	[[Distributed Computing]]<br />
		+	[[IT Operations (Information Technology Operations)]]<br />
		+	[[IT Sourcing (Information Technology Sourcing)]]<br />
		+	[[IT Strategy (Information Technology Strategy)]]<br />
		+
		+
		+	== References ==
		+	<references/>

@@ Line 1: / Line 1: @@
 == Definition of Microservices<ref>What are Microservices? [https://microservices.io/ Microservices.io]</ref> ==
-'''Microservices''' - also known as the '''microservice architecture''' - is an [[Architectural Style|architectural style]] that structures an [[Application}application]] as a collection of [[Service|services]] that are:
+'''Microservices''' - also known as the '''microservice architecture''' - is an [[Architectural Style|architectural style]] that structures an [[Application|application]] as a collection of [[Service|services]] that are:
 *Highly maintainable and testable
 *Loosely coupled
@@ Line 24: / Line 24: @@
 The difference between microservices and monolithic architecture is that microservices compose a single application from many smaller, loosely coupled services as opposed to the monolithic approach of a large, tightly coupled application
-The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)}enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.
+The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)|enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.
@@ Line 41: / Line 41: @@
 In February 2020, the Cloud Microservices Market Research Report predicted that the global microservice architecture market size will increase at a [[Compound Annual Growth Rate (CAGR)|CAGR]] of 21.37% from 2019 to 2026 and reach $3.1 billion by 2026.

@@ Line 9: / Line 9: @@
-[[File:File.png|200px|thumb|left|alt text]]<br />
+[[File:Microservices.png|400px|Microservices]]<br />
 source: [https://dzone.com/articles/what-are-microservices-actually DZone]
@@ Line 25: / Line 25: @@
 The differences between microservices and SOA can be a bit less clear. While technical contrasts can be drawn between microservices and SOA, especially around the role of the [[Enterprise Service Bus (ESB)}enterprise service bus (ESB)]], it’s easier to consider the difference as one of scope. SOA was an enterprise-wide effort to standardize the way all web services in an organization talk to and integrate with each other, whereas microservices architecture is application-specific.