|
|
|
|
| LEADER |
02333nmm a2200337 u 4500 |
| 001 |
EB001934448 |
| 003 |
EBX01000000000000001097350 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 9781492075400
|
| 050 |
|
4 |
|a QA76.9.A73
|
| 100 |
1 |
|
|a Mitra, Ronnie
|
| 245 |
0 |
0 |
|a Microservices
|b Up and Running
|c Mitra, Ronnie
|
| 250 |
|
|
|a 1st edition
|
| 260 |
|
|
|b O'Reilly Media, Inc.
|c 2020
|
| 300 |
|
|
|a 255 pages
|
| 653 |
|
|
|a Software architecture / http://id.loc.gov/authorities/subjects/sh2004001071
|
| 653 |
|
|
|a Software architecture / fast
|
| 653 |
|
|
|a Architecture logicielle
|
| 700 |
1 |
|
|a Nadareishvili, Irakli
|e author
|
| 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 9781492075455
|
| 776 |
|
|
|z 1492075450
|
| 776 |
|
|
|z 9781492075400
|
| 776 |
|
|
|z 149207540X
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781492075448/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 004.654
|
| 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"?
|