|
|
|
|
| LEADER |
02117nmm a2200253 u 4500 |
| 001 |
EB002216790 |
| 003 |
EBX01000000000000001353751 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
240701 ||| eng |
| 020 |
|
|
|a 9781663735614
|
| 050 |
|
4 |
|a QA76.76.A65
|
| 100 |
1 |
|
|a Wells, Sarah
|
| 245 |
0 |
0 |
|a Enabling Microservice Success
|b managing technical organizational, and cultural challenges
|c Sarah Wells ; foreword by Sam Newman
|
| 260 |
|
|
|a [Regon Park, New York]
|b Ascent Audio
|c 2024
|
| 300 |
|
|
|a 1 audio file
|
| 653 |
|
|
|a Application software / Development / http://id.loc.gov/authorities/subjects/sh95009362
|
| 653 |
|
|
|a Logiciels d'application / Développement
|
| 700 |
1 |
|
|a Newman, Sam
|e writer of foreword
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781663735614/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.3
|
| 520 |
|
|
|a Microservices can be a very effective approach for delivering value to your organization and to your customers. If you get them right, microservices help you to move fast, making changes to small parts of your system hundreds of times a day. But get them wrong and microservices just make everything more complicated. In this book, technical strategist Sarah Wells provides practical, in-depth advice for moving to microservices. Having built her first microservices architecture in 2013 for the Financial Times, Sarah discusses the approaches you need to take from the start, and explains the potential traps most likely to trip you up. You'll also learn how to maintain the architecture as your systems mature while minimizing the time you spend on support and maintenance. With this book, you will: - Learn the impact of microservices on software development patterns and practices - Identify the organizational changes you need to make to successfully build and operate this architecture - Determine the steps you must take before you move to microservices - Understand the traps to avoid when you create a microservices architecture-and learn how to recover if you fall into one
|