Cargando…
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...
| Autor principal: | |
|---|---|
| Autor Corporativo: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
O'Reilly Media, Inc.,
2020.
|
| Edición: | 1st edition. |
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cam a22000007a 4500 | ||
|---|---|---|---|
| 001 | OR_on1192527082 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o d | ||
| 007 | cr cnu|||||||| | ||
| 008 | 180820s2020 xx o 000 0 eng | ||
| 040 | |a AU@ |b eng |c AU@ |d UAB |d OCLCO |d OCLCF |d OCLCO |d OCLCQ |d TOH |d OCLCQ | ||
| 020 | |z 9781492085287 | ||
| 024 | 8 | |a 9781492085294 | |
| 029 | 0 | |a AU@ |b 000067830374 | |
| 035 | |a (OCoLC)1192527082 | ||
| 049 | |a UAMI | ||
| 100 | 1 | |a Schutta, Nathaniel, |e author. | |
| 245 | 1 | 0 | |a Responsible Microservices / |c Schutta, Nathaniel. |
| 250 | |a 1st edition. | ||
| 264 | 1 | |b O'Reilly Media, Inc., |c 2020. | |
| 300 | |a 1 online resource (66 pages) | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 347 | |a text file | ||
| 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 | ||
| 542 | |f Copyright © O'Reilly Media, Inc. | ||
| 550 | |a Made available through: Safari, an O'Reilly Media Company. | ||
| 588 | |a Online resource; Title from title page (viewed August 25, 2020) | ||
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 0 | |a Software architecture. | |
| 650 | 6 | |a Architecture logicielle. | |
| 650 | 7 | |a Software architecture. |2 fast |0 (OCoLC)fst01200416 | |
| 710 | 2 | |a Safari, an O'Reilly Media Company. | |
| 856 | 4 | 0 | |u https://learning.oreilly.com/library/view/~/9781492085294/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 936 | |a BATCHLOAD | ||
| 994 | |a 92 |b IZTAP | ||