File tree Expand file tree Collapse file tree 4 files changed +24
-1
lines changed
source/content/pages/07-web-app-deployment Expand file tree Collapse file tree 4 files changed +24
-1
lines changed Original file line number Diff line number Diff line change @@ -7796,6 +7796,14 @@ <h3>Microservice resources</h3>
77967796 and why to consider them as an architectural pattern.</ p >
77977797</ li >
77987798< li >
7799+ < p > < a href ="http://dev.otto.de/2016/03/20/why-microservices/ "> Why microservices?</ a >
7800+ presents some of the advantages, such as the dramatically increased number
7801+ of deployments per day, that a well-done microservices architecture can
7802+ provide in the right situation. Many organizational environments won't
7803+ allow this level of flexibility but if yours is one that will, it's worth
7804+ considering these points.</ p >
7805+ </ li >
7806+ < li >
77997807< p > < a href ="http://dev.otto.de/2015/09/30/on-monoliths-and-microservices/ "> On monoliths and microservices</ a >
78007808 provides some advice on using microservices in a fairly early stage of
78017809 a software project's lifecycle.</ p >
Original file line number Diff line number Diff line change 11<?xml version =" 1.0" encoding =" utf-8" ?>
2- <feed xmlns =" http://www.w3.org/2005/Atom" ><title >Matt Makai</title ><link href =" http://www.fullstackpython.com/" rel =" alternate" ></link ><link href =" http://www.fullstackpython.com/feeds/all.atom.xml" rel =" self" ></link ><id >http://www.fullstackpython.com/</id ><updated >2016-03-22T17:09:51Z </updated ></feed >
2+ <feed xmlns =" http://www.w3.org/2005/Atom" ><title >Matt Makai</title ><link href =" http://www.fullstackpython.com/" rel =" alternate" ></link ><link href =" http://www.fullstackpython.com/feeds/all.atom.xml" rel =" self" ></link ><id >http://www.fullstackpython.com/</id ><updated >2016-03-23T17:25:06Z </updated ></feed >
Original file line number Diff line number Diff line change @@ -64,6 +64,14 @@ <h3>Microservice resources</h3>
6464 and why to consider them as an architectural pattern.</ p >
6565</ li >
6666< li >
67+ < p > < a href ="http://dev.otto.de/2016/03/20/why-microservices/ "> Why microservices?</ a >
68+ presents some of the advantages, such as the dramatically increased number
69+ of deployments per day, that a well-done microservices architecture can
70+ provide in the right situation. Many organizational environments won't
71+ allow this level of flexibility but if yours is one that will, it's worth
72+ considering these points.</ p >
73+ </ li >
74+ < li >
6775< p > < a href ="http://dev.otto.de/2015/09/30/on-monoliths-and-microservices/ "> On monoliths and microservices</ a >
6876 provides some advice on using microservices in a fairly early stage of
6977 a software project's lifecycle.</ p >
Original file line number Diff line number Diff line change @@ -42,6 +42,13 @@ ease further development and deployment. This approach is called the
4242 article is one of the best in-depth explanations for what microservices are
4343 and why to consider them as an architectural pattern.
4444
45+ * [ Why microservices?] ( http://dev.otto.de/2016/03/20/why-microservices/ )
46+ presents some of the advantages, such as the dramatically increased number
47+ of deployments per day, that a well-done microservices architecture can
48+ provide in the right situation. Many organizational environments won't
49+ allow this level of flexibility but if yours is one that will, it's worth
50+ considering these points.
51+
4552* [ On monoliths and microservices] ( http://dev.otto.de/2015/09/30/on-monoliths-and-microservices/ )
4653 provides some advice on using microservices in a fairly early stage of
4754 a software project's lifecycle.
You can’t perform that action at this time.
0 commit comments