【独家发布】【2016新书】NoSQL & SQL Data Modeling: Bringing Together Data, Semantics [推广有奖]

166
关注
1378
粉丝

泰斗

38%

还不是VIP/贵宾

TA的文库 其他...

经管之家送您一份

应届毕业生专属福利!

求职就业群

赵安豆老师微信：zhaoandou666

经管之家联合CDA

送您一个全额奖学金名额~ !

立即领取

感谢您参与论坛问题回答

经管之家送您两个论坛币！

+2 论坛币

如果喜欢该文档，欢迎订阅【2016新书】文库，https://bbs.pinggu.org/forum.php?mod=collection&action=view&ctid=3187

图书名称：NoSQL and SQL Data Modeling: Bringing Together Data, Semantics, and Software
作者：Ted Hills
出版社：Technics Publications
页数：258
出版时间：2016
语言：English
格式：pdf
内容简介：
How do we design for data when traditional design techniques cannot extend to new database technologies? In this era of big data and the Internet of Things, it is essential that we have the tools we need to understand the data coming to us faster than ever before, and to design databases and data processing systems that can adapt easily to ever-changing data schemas and ever-changing business requirements. There must be no intellectual disconnect between data and the software that manages it. It must be possible to extract meaning and knowledge from data to drive artificial intelligence applications. Novel NoSQL data organization techniques must be used side-by-side with traditional SQL databases. Are existing data modeling techniques ready for all of this? The Concept and Object Modeling Notation (COMN) is able to cover the full spectrum of analysis and design. A single COMN model can represent the objects and concepts in the problem space, logical data design, and concrete NoSQL and SQL document, key-value, columnar, and relational database implementations. COMN models enable an unprecedented level of traceability of requirements to implementation. COMN models can also represent the static structure of software and the predicates that represent the patterns of meaning in databases. This book will teach you:

the simple and familiar graphical notation of COMN with its three basic shapes and four line styles
how to think about objects, concepts, types, and classes in the real world, using the ordinary meanings of English words that aren't tangled with confused techno-speak
how to express logical data designs that are freer from implementation considerations than is possible in any other notation
how to understand key-value, document, columnar, and table-oriented database designs in logical and physical terms
how to use COMN to specify physical database implementations in any NoSQL or SQL database with the precision necessary for model-driven development

回复免费：