HPE MSA 1060 2060 2062 Storage Arrays Best Practices MSA存储最佳实践

Microsoft.Practices.ServiceLocation

2.2 Cokriging模型 Cokriging 模型是上个世纪 70 年代发展起来 的一种更有效的地质统计学插值模型 [91]-[95] 。在 地质统计学领域，为了提高对某个抽样比较困难 的量的预测精度，提出了采用更容易抽样的量进 行辅助预测的 kriging 模型，称为 cokriging 模型 [92] 。2000 年，Kennedy 和 O’Hagan[96]首次将 cokriging 模型推广应用于工程科学领域，发展了 一种采用低可信度计算机程序结果，来辅助预测 高可信度计算机程序结果的 cokriging 方法。目前 国际上对 cokriging 模型的研究主要集中在地质统 计学和数学统计学等领域，在航空航天等工程科 学领域的研究也逐渐得到重视 [14][97]-[101] 。 2010 年，文献[101]独立提出了一种可用于 建立变可信度代理模型的实用 cokriging 模型（也 参见[14]）。下面对该模型进行介绍。 对于一个具有 m 个设计变量的优化问题， 在设计空间中同时采用高可信度分析（例如 NS 方程或密网格数值模拟）和低可信度分析（例如 Euler 方程或疏网格数值模拟）进行抽样，并建 立所谓的变可信度代理模型。更多建立变可信度 模型的方法请参见文献[88]。变可信度代理模型 在达到相同近似精度的条件下，可显著提高建立 代理模型的效率。 假设高、低可信度分析程序的抽样位置如下 1 1 2 2 ( )(1) T 1 1 1 ( )(1) T 2 2 2 ( ,..., ) ( ,..., )       S x x S x x   n n m n n m (40) 下标“1”和“2”分别代表高、低可信度，例如 1n 和 2n 分别代表高、低可信度样本点数（假设 2 1n n ）。相应的目标函数或约束函数的响应值 如下 1 1 2 2 ( )(1) T 1 1 1 ( )(1) T 2 2 2 [ ,..., ] , [ ,..., ] .     y y   n n n n y y y y (41) Cokriging 模型预估值定义如下 T T T 1 1 1 2 2ˆ ( )   x λ y λ y λ ySy , (42) 其中 1 2,λ λ 分别为对高、低可信度响应值的加权 系数。假设存在分别与 ,y y1 2 分别对应的 2 个 静态随机过程， ( ) ( ), ( ) ( ).       x x x x Y Z Y Z 1 1 1 2 2 2 (43) 则设计空间不同位置处，随机变量之间的协方差 和交叉协方差定义为 ( ) ( ) ( ) ( )2 (11) 11 1 1 1 ( ) ( ) ( ) ( )2 (22) 22 2 2 2 ( ) ( ) ( ) ( )(12) 1 21 2 1 2 ( ( ), ( )) ( , ) ( ( ), ( )) ( , ) ( ( ), ( )) ( , )        x x x x x x x x x x x x i j i j i j i j i j i j Cov Z Z R Cov Z Z R Cov Z Z R (44) 其中， 21 和 2 2 分别为随机过程 ( )xY1 和 ( )xY2 的过程方差。采用与 kriging 模型类似的推 导方法，可得到 cokriging 模型的预估值如下（具 体推导过程见文献[14]） T T 1 1 Sˆ ( ) ( ) ( )   x φ β r x R y Fβy ， (45) 其中 1 2 1T 1 1 T 11 S 22 1(11) (12) ( ) 2 S 1(21) (22) 2 2 ( )1 , ( ) , , ( )0 , , ,                                                r x φ β F R F F R y r r x y R R 1 0 R y F y 0 1R R      n n (46) 且有

动手的RESTful API设计模式和最佳实践 这是Packt发布的“ 的代码存储库。 设计，开发和部署高度适应性，可扩展性和安全性的RESTful Web API 这本书是关于什么的？ 本书介绍了代表性状态传输（REST）范例，该范例是一种体系结构样式，允许联网的设备通过Internet相互通信。 在本书的帮助下，您将探索面向服务的体系结构（SOA），事件驱动的体系结构（EDA）和面向资源的体系结构（ROA）的概念。 本书涵盖了为什么需要高质量的API来进行企业集成。 本书涵盖以下激动人心的功能： 探索RESTful概念，包括URI，HATEOAS和按需编码 研究无状态，分页和可发现性等核心模式 使用API​​网关优化链接微服务的端点 深入研究API身份验证，授权和API安全性实施 与服务编排一起制定复合和流程感知服务 公开用于云计算的基于RESTful协议的API 如果您觉

Function Point Counting Practices Manual 4.3.pdf

SAE J3187-2022 System Theoretic Process Analysis (STPA) Recommended Practices for Evaluations of Automotive Related Safety-Criti.pdf

Many programmers code by instinct, relying on convenient habits or a "style" they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. But if you're serious about your profession, intuition isn't enough. Perl Best Practices author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, Perl Best Practices offers coherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how software ought to be created. Most of all, Perl Best Practices offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. Praise for Perl Best Practices from Perl community members: "As a manager of a large Perl project, I'd ensure that every member of my team has a copy of Perl Best Practices on their desk, and use it as the basis for an in-house style guide." -- Randal Schwartz "There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book." -- Peter Scott "Perl Best Practices will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of "scripting languages". Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too." -- Andy Lester "Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years." -- Bill Odom "Finally, a means to bring lasting order to the process and product of real Perl development teams." -- Andrew Sundstrom"Perl Best Practices provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers." -- Bennett Todd "I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer." -- Paul Fenwick "At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues." -- Jacinta Richardson "If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it." -- Steven Lembark "The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until Perl Best Practices. This book fills a large gap in every Perl bookshelf." -- Uri Guttman

Efficient MySQL Performance Best Practices and Techniques 2021 PDF格式，好书

设计的Lumen Api起动器 :red_heart_selector: 发现了网上很多的API相关的开发规范文档，参考了很多大佬们总结的经验，决定尝试使用最新版本的Lumen（当下最新版本是Lumen 8.x）来构建一个基础功能完备，规范统一，能够快速调整实际的API项目开发启动模板。同时，也希望通过合理的架构设计调整适用于中大型项目。 稍微的依赖安装，取决于Laravel的思维进行扩展，不额外增加“负担”。 开箱即用，加速Api开发。 社区讨论传送 Lumen学习交流群：1105120693（QQ） 概览 初步支持 适应Laravel 7中新增的HttpClient客户端（已升级到Laravel 8） RESTful规范的路由定义和HTTP响应结构 使用Laravel Api资源 支持自定义业务操作应码以及业务操作描述（多语言支持，根据配置中的APP_LOCAL配置返回） Jwt-auth方式授权（支持将授权用户缓存到redis，减少用户表查询频次） 更加便捷地使用枚举/常量：方便地对枚举进行判断校正；请求中包含枚举参数可以自动转换为对应枚举实例 支持日志记录到MongoDB

Microservice architecture has emerged as a common pattern of software develop‐ ment from the practices of a number of leading organizations. These practices includes principles, technologies, methodologies, organizational tendencies, and cul‐ tural characteristics. Companies taking steps to implement microservices and reap their benefits need to consider this broad scope. Who Should Read This Book You should read this book if you are interested in the architectural, organizational, and cultural changes that are needed to succeed with a microservice architecture. We primarily wrote this book for technology leaders and software architects who want to shift their organizations toward the microservices style of application development. You don’t have to be a CTO or enterprise architect to enjoy this book, but we’ve writ‐ ten our guidance under the assumption that you are able to influence the organiza‐ tional design, technology platform, and software architecture at your company. What’s In This Book This book promotes a goal-oriented, design-based approach to microservice architec‐ ture. We offer this design-centric approach because, as we talked to several companies about their programs, we discovered one of the keys to their success was the willing‐ ness to not stick to a single tool or process as they attempted to increase their compa‐ ny’s time-to-market while maintaining—even increasing—their systems’ safety and resilience. The companies we talked to offered a wide range of services including live video and audio streaming service, foundation-level virtual services in the cloud, and support for classic brick-and-mortar operations. While these companies’ products vary, we learned that the principles of speed and safety “at scale” were a common thread. They ix each worked to provide the same system properties in their own unique ways—ways that fit the key business values and goals of the company. It’s the properties and values that we focus on in this book, and the patterns and prac‐ tices we see companies employ in order to reach their unique goals. If you’re looking for a way to identify business goals for your microservices adoption, practical guid‐ ance on how to design individual microservices and the system they form, and tips on how to overcome common architectural challenges, this is your book! The Outline The book is organized into three parts. The first part (Chapters 1–2) identifies the principles and practices of microservice architecture and the benefits they can pro‐ vide. This section will be valuable to anyone who needs to justify the use of microser‐ vices within their organization and provide some background on how other organizations have started on this journey. The second part (Chapters 3–4) introduces a design-based approach to microservice architecture, identifies a series of common processes and practices we see repeated through successful microservice systems, and provides some implementation guid‐ ance on executing the various elements for your company’s microservice implemen‐ tation. The third and final part (Chapters 5–7) provides a set of practical recipes and practi‐ ces to help companies identify ways to introduce and support microservices, meet immediate challenges, and plan for and respond to the inevitably changing business environment ahead. Here’s a quick rundown of the chapters: Chapter 1, The Microservices Way This chapter outlines the principles, practices, and culture that define microser‐ vice architecture. Chapter 2, The Microservices Value Proposition This chapter examines the benefits of microservice architecture and some techni‐ ques to achieve them. Chapter 3, Designing Microservice Systems This chapter explores the system aspects of microservices and illustrates a design process for microservice architecture. Chapter 4, Establishing a Foundation This chapter discusses the core principles for microservice architecture, as well as the platform components and cultural elements needed to thrive. x | Preface Chapter 5, Service Design This chapter takes the “micro” design view, examining the fundamental design concepts for individual microservices. Chapter 6, System Design and Operations This chapter takes the “macro” design view, analyzing the critical design areas for the software system made up of the collection of microservices. Chapter 7, Adopting Microservices in Practice This chapter provides practical guidance on how to deal with common chal‐ lenges organizations encounter as they introduce microservice architecture. Chapter 8, Epilogue Finally, this chapter examines microservices and microservice architecture in a timeless context, and emphasizes the central theme of the book: adaptability to change. What’s Not In This Book The aim of this book is to arm readers with practical information and a way of think‐ ing about microservices that is timeless and effective. This is not a coding book. There is a growing body of code samples and open source projects related to micro‐ services available on the Web, notably on GitHub and on sites like InfoQ. In addition, the scope of this domain is big and we can only go so deep on the topics we cover. For more background on the concepts we discuss, check out our reading list in Appen‐ dix A. While we provide lots of guidance and advice—advice based on our discussions with a number of companies designing and implementing systems using microservice architecture patterns—we do not tell readers which product to buy, which open source project to adopt, or how to design and test component APIs. Instead, we offer insight into the thinking processes and practices of experienced and successful com‐ panies actually doing the work of microservices. If you’re looking for simple answers, you’re likely to be disappointed in some of the material here. If, on the other hand, you’re looking for examples of successful microservice companies and the kinds of principles, practices, and processes they employ, this book is for you.