دسترسی نامحدود
برای کاربرانی که ثبت نام کرده اند
برای ارتباط با ما می توانید از طریق شماره موبایل زیر از طریق تماس و پیامک با ما در ارتباط باشید
در صورت عدم پاسخ گویی از طریق پیامک با پشتیبان در ارتباط باشید
برای کاربرانی که ثبت نام کرده اند
درصورت عدم همخوانی توضیحات با کتاب
از ساعت 7 صبح تا 10 شب
ویرایش: 1 نویسندگان: Murat Erder, Pierre Pureur, Eoin Woods سری: Addison-Wesley Signature Series (Vernon) ISBN (شابک) : 0136523560, 9780136523567 ناشر: Addison-Wesley Professional سال نشر: 2021 تعداد صفحات: 0 زبان: English فرمت فایل : EPUB (درصورت درخواست کاربر به PDF، EPUB یا AZW3 تبدیل می شود) حجم فایل: 11 مگابایت
در صورت تبدیل فایل کتاب Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps به فرمت های PDF، EPUB، AZW3، MOBI و یا DJVU می توانید به پشتیبان اطلاع دهید تا فایل مورد نظر را تبدیل نمایند.
توجه داشته باشید کتاب معماری مستمر در عمل: معماری نرم افزار در عصر چابکی و DevOps نسخه زبان اصلی می باشد و کتاب ترجمه شده به فارسی نمی باشد. وبسایت اینترنشنال لایبرری ارائه دهنده کتاب های زبان اصلی می باشد و هیچ گونه کتاب ترجمه شده یا نوشته شده به فارسی را ارائه نمی دهد.
\"این کتاب تشخیص میدهد که معماری نرمافزار صرفاً حوزه مفهومی متخصصان غیرمرتبط نیست، بلکه درگیری روزانه اعضای تیم است که باید بین مبادلات و نیروهای رقیب تعادل برقرار کنند تا بتوانند انعطافپذیر را ارائه دهند. برنامه های کاربردی با کارایی بالا و ایمن... [این] شکاف قابل توجهی را بین نمای «زمین از مدار» و نمای سطح روسازی کد میکروسرویس بازسازی مجدد پل می کند.\"نویسندگان Murat Erder، Pierre Pureur و Eoin Woods از تجربه گسترده معماری سازمانی خود استفاده کرده اند و آن را در جنبه های عملی معماری پیوسته در محیط های دنیای واقعی به کار برده اند. . معماری مستمر در عمل توصیههای عملی برای استفاده از معماری پیوسته در محیطهای دنیای واقعی ارائه میکند و نقش متغیر معماری را در عصر چابک، DevSecOps و پلتفرمهای ابری روشن میکند. این راهنما به فنآوران کمک میکند تا شیوه معماری خود را برای چالشهای کاربردی جدید بهروزرسانی کنند. به عنوان بخشی از سری امضای Vaughn Vernon Addison-Wesley، این عنوان برای دانش عملی و تحویل محور که معماران و مهندسان نرم افزار می توانند به سرعت به کار گیرند، به صورت دستی انتخاب شده است. این شامل راهنمایی های عمیق برای پرداختن به ویژگی های کیفیت کلیدی امروزی، از جمله نگرانی های مقطعی مانند امنیت، عملکرد، مقیاس پذیری، انعطاف پذیری، داده ها و نوآوری است. هر تکنیک کلیدی از طریق یک مطالعه موردی شروع تا پایان نشان داده شده است که منعکس کننده تجربه عمیق نویسندگان در تکامل محیط های نرم افزاری پیچیده است.
--Kurt Bittner, VP , Enterprise Solutions, Scrum.org
"This book recognizes that software architecture is not the merely conceptual domain of disconnected experts but is the . . . give-and-take daily tussle of team members who have to balance trade-offs and competing forces to deliver resilient, high-performing, secure applications. . . . [It] bridges the significant gap between the 'Earth from orbit' view and the pavement-level view of refactoring microservice code."Authors Murat Erder, Pierre Pureur, and Eoin Woods have taken their extensive enterprise architecture experience and applied it to the practical aspects of continuous architecture in real-world environments. Continuous Architecture in Practice provides hands-on advice for leveraging continuous architecture in real-world environments and illuminates architecture's changing role in the age of Agile, DevSecOps, and cloud platforms. This guide will help technologists update their architecture practice for new application challenges. As part of the Vaughn Vernon Addison-Wesley Signature Series, this title was hand-selected for the practical, delivery-oriented knowledge that architects and software engineers can quickly apply. It includes in-depth guidance for addressing today's key quality attributes, including cross-cutting concerns such as security, performance, scalability, resilience, data, and innovation. Each key technique is demonstrated through a start-to-finish case study reflecting the authors' deep experience evolving complex software environments.
--Kurt Bittner, VP, Enterprise Solutions, Scrum.org
Cover Half Title Title Copyright Dedication Contents Series Editor Foreword Foreword Introduction Acknowledgments About the Authors Chapter 1: Why Software Architecture Is More Important than Ever What Do We Mean by Architecture? Software Industry Today Current Challenges with Software Architecture Focus on Technology Details Rather than Business Context Perception of Architects as Not Adding Value Architectural Practices May Be Too Slow Some Architects May Be Uncomfortable with Cloud Platforms Software Architecture in an (Increasingly) Agile World The Beginnings: Software Architecture and Extreme Programming Where We Are: Architecture, Agility, and Continuous Delivery Where We May Be Going Introducing Continuous Architecture Continuous Architecture Definition Continuous Architecture Benefits Applying Continuous Architecture Continuous Architecture Provides a Set of Principles and Tools Introduction to the Case Study Case Study Context: Automating Trade Finance Summary Chapter 2: Architecture in Practice: Essential Activities Essential Activities Overview Architectural Decisions Making and Governing Architectural Decisions Quality Attributes Quality Attributes and Architectural Tactics Working with Quality Attributes Building the Quality Attributes Utility Tree Technical Debt Capturing Technical Debt How to Manage Technical Debt Feedback Loops: Evolving an Architecture Fitness Functions Continuous Testing Common Themes in Today’s Software Architecture Practice Principles as Architecture Guidelines Team-Owned Architecture Models and Notations Patterns and Styles Architecture as a Flow of Decisions Summary Chapter 3: Data Architecture Data as an Architectural Concern What Is Data? Common Language Key Technology Trends Demise of SQL’s Dominance: NoSQL and Polyglot Persistence Scale and Availability: Eventual Consistency Events versus State: Event Sourcing Data Analytics: Wisdom and Knowledge from Information Additional Architectural Considerations Data Ownership and Metadata Data Integration Data (Schema) Evolution Summary Further Reading Chapter 4: Security as an Architectural Concern Security in an Architectural Context What’s Changed: Today’s Threat Landscape What Do We Mean by Security? Moving Security from No to Yes Shifting Security Left Architecting for Security What Is a Security Threat? Continuous Threat Modeling and Mitigation Techniques for Threat Identification Prioritizing Threats Other Approaches Architectural Tactics for Mitigation Authentication, Authorization, and Auditing Information Privacy and Integrity Nonrepudiation System Availability Security Monitoring Secrets Management Social Engineering Mitigation Zero Trust Networks Achieving Security for TFX Maintaining Security Secure Implementation People, Process, Technology The Weakest Link Delivering Security Continuously Being Ready for the Inevitable Failure Security Theater versus Achieving Security Summary Further Reading Chapter 5: Scalability as an Architectural Concern Scalability in the Architectural Context What Changed: The Assumption of Scalability Forces Affecting Scalability Types and Misunderstandings of Scalability The Effect of Cloud Computing Architecting for Scalability: Architecture Tactics TFX Scalability Requirements Database Scalability Data Distribution, Replication, and Partitioning Caching for Scalability Using Asynchronous Communications for Scalability Additional Application Architecture Considerations Achieving Scalability for TFX Summary Further Reading Chapter 6: Performance as an Architectural Concern Performance in the Architectural Context Forces Affecting Performance Architectural Concerns Architecting for Performance Performance Impact of Emerging Trends Architecting Applications around Performance Modeling and Testing Modern Application Performance Tactics Modern Database Performance Tactics Achieving Performance for TFX Summary Further Reading Chapter 7: Resilience as an Architectural Concern Resilience in an Architectural Context What Changed: The Inevitability of Failure Reliability in the Face of Failure The Business Context MTTR, Not (Just) MTBF MTBF and MTTR versus RPO and RTO Getting Better over Time The Resilient Organization Architecting for Resilience Allowing for Failure Measurement and Learning Architectural Tactics for Resilience Fault Recognition Tactics Isolation Tactics Protection Tactics Mitigation Tactics Achieving Resilience for TFX Maintaining Resilience Operational Visibility Testing for Resilience The Role of DevOps Detection and Recovery, Prediction and Mitigation Dealing with Incidents Disaster Recovery Summary Further Reading Chapter 8: Software Architecture and Emerging Technologies Using Architecture to Deal with Technical Risk Introduced by New Technologies Introduction to Artificial Intelligence, Machine Learning, and Deep Learning Types of Machine Learning What about Deep Learning? Using Machine Learning for TFX Types of Problems Solved by ML, Prerequisites and Architecture Concerns Using Document Classification for TFX Implementing a Chatbot for TFX Using a Shared Ledger for TFX Brief Introduction to Shared Ledgers, Blockchain, and Distributed Ledger Technology Types of Problems Solved by Shared Ledgers, Prerequisites, and Architectural Concerns Shared Ledger Capabilities Implementing a Shared Ledger for TFX Benefits of an Architecture-Led Approach Summary Further Reading Chapter 9: Conclusion What Changed and What Remained the Same Updating Architecture Practice Data Key Quality Attributes Security Scalability Performance Resilience The Architect in the Modern Era Putting Continuous Architecture in Practice Appendix A: Case Study Appendix B: Comparison of Technical Implementations of Shared Ledgers Glossary A B C D E F H I K M P Q R S T U Index A B C D E F G H I J-K L M N O P Q R S T U-V-W X-Y-Z