Gespeichert in:
| Beteilige Person: | |
|---|---|
| Körperschaft: | |
| Format: | Elektronisch E-Book |
| Sprache: | Englisch |
| Veröffentlicht: |
[Erscheinungsort nicht ermittelbar]
O'Reilly Media, Inc.
2020
|
| Ausgabe: | 1st edition. |
| Schlagwörter: | |
| Links: | https://learning.oreilly.com/library/view/-/9781492085294/?ar |
| Zusammenfassung: | 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 |
| Beschreibung: | Online resource; Title from title page (viewed August 25, 2020) |
| Umfang: | 1 Online-Ressource (66 pages) |
Internformat
MARC
| LEADER | 00000cam a22000002c 4500 | ||
|---|---|---|---|
| 001 | ZDB-30-ORH-056583583 | ||
| 003 | DE-627-1 | ||
| 005 | 20240228121137.0 | ||
| 007 | cr uuu---uuuuu | ||
| 008 | 200916s2020 xx |||||o 00| ||eng c | ||
| 035 | |a (DE-627-1)056583583 | ||
| 035 | |a (DE-599)KEP056583583 | ||
| 035 | |a (ORHE)9781492085294 | ||
| 035 | |a (DE-627-1)056583583 | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rda | ||
| 041 | |a eng | ||
| 100 | 1 | |a Schutta, Nathaniel |e VerfasserIn |4 aut | |
| 245 | 1 | 0 | |a Responsible Microservices |c Schutta, Nathaniel |
| 250 | |a 1st edition. | ||
| 264 | 1 | |a [Erscheinungsort nicht ermittelbar] |b O'Reilly Media, Inc. |c 2020 | |
| 300 | |a 1 Online-Ressource (66 pages) | ||
| 336 | |a Text |b txt |2 rdacontent | ||
| 337 | |a Computermedien |b c |2 rdamedia | ||
| 338 | |a Online-Ressource |b cr |2 rdacarrier | ||
| 500 | |a Online resource; Title from title page (viewed August 25, 2020) | ||
| 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 | ||
| 650 | 0 | |a Software architecture | |
| 650 | 4 | |a Architecture logicielle | |
| 650 | 4 | |a Software architecture | |
| 710 | 2 | |a Safari, an O'Reilly Media Company. |e MitwirkendeR |4 ctb | |
| 966 | 4 | 0 | |l DE-91 |p ZDB-30-ORH |q TUM_PDA_ORH |u https://learning.oreilly.com/library/view/-/9781492085294/?ar |m X:ORHE |x Aggregator |z lizenzpflichtig |3 Volltext |
| 912 | |a ZDB-30-ORH | ||
| 912 | |a ZDB-30-ORH | ||
| 951 | |a BO | ||
| 912 | |a ZDB-30-ORH | ||
| 049 | |a DE-91 | ||
Datensatz im Suchindex
| DE-BY-TUM_katkey | ZDB-30-ORH-056583583 |
|---|---|
| _version_ | 1835903154686787584 |
| adam_text | |
| any_adam_object | |
| author | Schutta, Nathaniel |
| author_corporate | Safari, an O'Reilly Media Company |
| author_corporate_role | ctb |
| author_facet | Schutta, Nathaniel Safari, an O'Reilly Media Company |
| author_role | aut |
| author_sort | Schutta, Nathaniel |
| author_variant | n s ns |
| building | Verbundindex |
| bvnumber | localTUM |
| collection | ZDB-30-ORH |
| ctrlnum | (DE-627-1)056583583 (DE-599)KEP056583583 (ORHE)9781492085294 |
| edition | 1st edition. |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02449cam a22003732c 4500</leader><controlfield tag="001">ZDB-30-ORH-056583583</controlfield><controlfield tag="003">DE-627-1</controlfield><controlfield tag="005">20240228121137.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">200916s2020 xx |||||o 00| ||eng c</controlfield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)056583583</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)KEP056583583</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ORHE)9781492085294</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)056583583</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Schutta, Nathaniel</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Responsible Microservices</subfield><subfield code="c">Schutta, Nathaniel</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">1st edition.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">[Erscheinungsort nicht ermittelbar]</subfield><subfield code="b">O'Reilly Media, Inc.</subfield><subfield code="c">2020</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (66 pages)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Online resource; Title from title page (viewed August 25, 2020)</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="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</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Software architecture</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Architecture logicielle</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software architecture</subfield></datafield><datafield tag="710" ind1="2" ind2=" "><subfield code="a">Safari, an O'Reilly Media Company.</subfield><subfield code="e">MitwirkendeR</subfield><subfield code="4">ctb</subfield></datafield><datafield tag="966" ind1="4" ind2="0"><subfield code="l">DE-91</subfield><subfield code="p">ZDB-30-ORH</subfield><subfield code="q">TUM_PDA_ORH</subfield><subfield code="u">https://learning.oreilly.com/library/view/-/9781492085294/?ar</subfield><subfield code="m">X:ORHE</subfield><subfield code="x">Aggregator</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">BO</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield></record></collection> |
| id | ZDB-30-ORH-056583583 |
| illustrated | Not Illustrated |
| indexdate | 2025-06-25T12:14:45Z |
| institution | BVB |
| language | English |
| open_access_boolean | |
| owner | DE-91 DE-BY-TUM |
| owner_facet | DE-91 DE-BY-TUM |
| physical | 1 Online-Ressource (66 pages) |
| psigel | ZDB-30-ORH TUM_PDA_ORH ZDB-30-ORH |
| publishDate | 2020 |
| publishDateSearch | 2020 |
| publishDateSort | 2020 |
| publisher | O'Reilly Media, Inc. |
| record_format | marc |
| spelling | Schutta, Nathaniel VerfasserIn aut Responsible Microservices Schutta, Nathaniel 1st edition. [Erscheinungsort nicht ermittelbar] O'Reilly Media, Inc. 2020 1 Online-Ressource (66 pages) Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Online resource; Title from title page (viewed August 25, 2020) 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 Software architecture Architecture logicielle Safari, an O'Reilly Media Company. MitwirkendeR ctb |
| spellingShingle | Schutta, Nathaniel Responsible Microservices Software architecture Architecture logicielle |
| title | Responsible Microservices |
| title_auth | Responsible Microservices |
| title_exact_search | Responsible Microservices |
| title_full | Responsible Microservices Schutta, Nathaniel |
| title_fullStr | Responsible Microservices Schutta, Nathaniel |
| title_full_unstemmed | Responsible Microservices Schutta, Nathaniel |
| title_short | Responsible Microservices |
| title_sort | responsible microservices |
| topic | Software architecture Architecture logicielle |
| topic_facet | Software architecture Architecture logicielle |
| work_keys_str_mv | AT schuttanathaniel responsiblemicroservices AT safarianoreillymediacompany responsiblemicroservices |