|
|
|
|
LEADER |
00000cam a2200000 i 4500 |
001 |
OR_on1125343549 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr unu|||||||| |
008 |
191030s2019 cau o 000 0 eng d |
040 |
|
|
|a UMI
|b eng
|e rda
|e pn
|c UMI
|d OCLCF
|d CZL
|d TOH
|d OCLCQ
|d OCLCO
|d OCLCQ
|d OCLCO
|
019 |
|
|
|a 1129195860
|
020 |
|
|
|z 9781492073499
|
035 |
|
|
|a (OCoLC)1125343549
|z (OCoLC)1129195860
|
037 |
|
|
|a CL0501000079
|b Safari Books Online
|
050 |
|
4 |
|a HD30.37
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Keune, Nicholas Alan,
|e author.
|
245 |
1 |
0 |
|a What are miniservices? :
|b Patterns for managing data across microservices and monoliths /
|c Nicholas Alan Keune.
|
246 |
3 |
0 |
|a Patterns for managing data across microservices and monoliths
|
250 |
|
|
|a First edition.
|
264 |
|
1 |
|a Sebastopol, CA :
|b O'Reilly Media,
|c [2019]
|
264 |
|
4 |
|c Ã2019
|
300 |
|
|
|a 1 online resource (1 volume)
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
588 |
0 |
|
|a Online resource; title from title page (Safari, viewed October 30, 2019).
|
520 |
|
|
|a Miniservices provide a valuable middle ground between monoliths and microservices. As Nicholas Keune explains in this report, miniservices are suited for application landscapes involving data-intensive workloads that span monoliths and microservices or cross the traditional boundaries of a service context. Drawn from the work of many development teams, the report gives a model and language to data-centric system attributes so that they can be considered more proactively in the design discussion. Combining monolithic corporate or third-party systems with microservices requires a design pattern to balance both local and global aspects of the data lifecycle. The approach advocated here, called a data discourse, is both flexible and bounded by guiding principles that help bring data discussions into early architectural conversations. Using real-world experiences and use cases, the report focuses on three of the most commonly observed attributes in a miniservice: consistency, transactionality, and proximity. The examples illustrate how design discussions about data discourses lead to miniservice creation, and how miniservices help solve otherwise difficult architectural challenges. With this report, you'll learn: What miniservices are and how they offer solutions to challenges What data discourses are and how to use them How data discourses and miniservices help shift design discussions around data.
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a Business enterprises
|x Data processing.
|
650 |
|
0 |
|a Electronic data processing
|x Distributed processing
|x Management.
|
650 |
|
0 |
|a Web services.
|
650 |
|
6 |
|a Entreprises
|x Informatique.
|
650 |
|
6 |
|a Services Web.
|
650 |
|
7 |
|a Business enterprises
|x Data processing
|2 fast
|
650 |
|
7 |
|a Electronic data processing
|x Distributed processing
|x Management
|2 fast
|
650 |
|
7 |
|a Web services
|2 fast
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781492073505/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
994 |
|
|
|a 92
|b IZTAP
|