|
|
|
|
LEADER |
00000cam a2200000 a 4500 |
001 |
OR_on1156476859 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr cnu|||||||| |
008 |
200520s2020 xx o 000 0 eng |
040 |
|
|
|a AU@
|b eng
|c AU@
|d YDX
|d YDXIT
|d OCLCF
|d OCLCO
|d OCLCQ
|
019 |
|
|
|a 1224578346
|
020 |
|
|
|a 9781492075400
|q (electronic bk.)
|
020 |
|
|
|a 149207540X
|q (electronic bk.)
|
020 |
|
|
|z 9781492075455
|
020 |
|
|
|z 1492075450
|
024 |
8 |
|
|a 9781492075448
|
029 |
0 |
|
|a AU@
|b 000067212130
|
035 |
|
|
|a (OCoLC)1156476859
|z (OCoLC)1224578346
|
050 |
|
4 |
|a QA76.9.A73
|b M58 2020
|
082 |
0 |
4 |
|a 004.654
|2 23
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Mitra, Ronnie,
|e author.
|
245 |
1 |
0 |
|a Microservices :
|b Up and Running /
|c Mitra, Ronnie.
|
250 |
|
|
|a 1st edition.
|
264 |
|
1 |
|b O'Reilly Media, Inc.,
|c 2020.
|
300 |
|
|
|a 1 online resource (255 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 Microservices architectures offer great benefits: faster change speeds, better scalability and cleaner, evolvable architectures. But, implementing your first Microservices architecture to get those rewards is difficult. How do you quickly educate your team on all the technical details of execution to maximize your chances of success? How do you survive the first year of bringing your microservices implementation to life? How do you improve your execution? Making the right implementation decisions is difficult and you don't have the luxury of time to find out if the decisions you are making are the right ones. This book offers a prescriptive guide for building a Microservices architecture to combat that uncertainty. Inside, you will find a step-by-step implementation journey mapped out based on the techniques and architectures that have been proven to work for Microservices systems. This book solves the following problems for users: What does a "good" microservices project look like? Are the decisions you're making for your project the "right" ones? How do you come up with a good microservices design that fits your own context as quickly as possible? Where should you spend time thinking/designing and where should you just implement "best practices"?
|
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 November 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
|
700 |
1 |
|
|a Nadareishvili, Irakli,
|e author.
|
710 |
2 |
|
|a Safari, an O'Reilly Media Company.
|
776 |
0 |
8 |
|c Original
|z 1492075450
|z 9781492075455
|w (OCoLC)1153060713
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781492075448/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
936 |
|
|
|a BATCHLOAD
|
938 |
|
|
|a YBP Library Services
|b YANK
|n 301772100
|
938 |
|
|
|a YBP Library Services
|b YANK
|n 17135023
|
994 |
|
|
|a 92
|b IZTAP
|