Responsible Microservices

These days, you can't swing a dry erase marker without hitting someone talking about microservices. But as developers write more code and build more applications than ever before, the trick is knowing which systems should use microservices and which shouldn't. This report provides a set of...

Full description

Bibliographic Details
Main Author: Schutta, Nathaniel
Format: eBook
Language:English
Published: O'Reilly Media, Inc. 2020
Edition:1st edition
Subjects:
Online Access:
Collection: O'Reilly - Collection details see MPG.ReNa
LEADER 02097nmm a2200277 u 4500
001 EB001943039
003 EBX01000000000000001105941
005 00000000000000.0
007 cr|||||||||||||||||||||
008 210123 ||| eng
050 4 |a QA76.754 
100 1 |a Schutta, Nathaniel 
245 0 0 |a Responsible Microservices  |c Schutta, Nathaniel 
250 |a 1st edition 
260 |b O'Reilly Media, Inc.  |c 2020 
300 |a 66 pages 
653 |a Software architecture / http://id.loc.gov/authorities/subjects/sh2004001071 
653 |a Architecture logicielle 
653 |a Software architecture / fast 
041 0 7 |a eng  |2 ISO 639-2 
989 |b OREILLY  |a O'Reilly 
500 |a Made available through: Safari, an O'Reilly Media Company 
776 |z 9781492085287 
856 4 0 |u https://learning.oreilly.com/library/view/~/9781492085294/?ar  |x Verlag  |3 Volltext 
082 0 |a 000 
520 |a These days, you can't swing a dry erase marker without hitting someone talking about microservices. But as developers write more code and build more applications than ever before, the trick is knowing which systems should use microservices and which shouldn't. This report provides a set of principles you can use to focus your efforts. Nataniel Schutta-prolific author, seasoned speaker, and proponent of polyglot programming-explains that while there are many good reasons to use microservices, this architecture can make things more complex. If you answer "yes" to one or more of the principles in this report, then your application is a good candidate for microservices. Answering "no" to every principle means you'd likely introduce accidental complexity into your system. This report helps you examine: Parts of your system that evolve at different speeds or in different directions Independent lifecycles among the features in your application Meeting demand by allowing components to scale independently Using an abstraction layer to isolate third-party dependencies Choosing different technologies to tackle different jobs The impact that a technological change has on company culture