This unique and critical book shares no-fail secrets for building software and offers tried-and-true practices and principles for software design, development, and testing for mission-critical systems that must not fail. A veteran software architect walks you through the lifecycle of a project as well as each area of production readiness—functionality, availability, performance and scalability, operability, maintainability, and extensibility, and highlights their key concepts.
In the past few years, going cloud native has been a big advantage for many companies. But it’s a tough technique to get right, especially for enterprises with critical legacy systems. This practical hands-on guide examines effective architecture, design, and cultural patterns to help you transform your organization into a cloud native enterprise—whether you’re moving from older architectures or creating new systems from scratch. By following Wealth Grid, a fictional company, you’ll understand the challenges, dilemmas, and considerations that accompany a move to the cloud. Technical managers and architects will learn best practices for taking on a successful company-wide transformation. Cloud migration consultants Pini Reznik, Jamie Dobson, and Michelle Gienow draw patterns from the growing community of expert practitioners and enterprises that have successfully built cloud native systems. You’ll learn what works and what doesn’t when adopting cloud native—including how this transition affects not just your technology but also your organizational structure and processes. You’ll learn: What cloud native means and why enterprises are so interested in it Common barriers and pitfalls that have affected other companies (and how to avoid them) Context-specific patterns for a successful cloud native transformation How to implement a safe, evolutionary cloud native approach How companies addressed root causes and misunderstandings that hindered their progress Case studies from real-world companies that have succeeded with cloud native transformations
With Managing IT as a Business you'll get practical advice on how to unleash the full potential of this critical function so that companies can derive maximum benefit. It offers a proven plan for bridging the gap between CEOs and CIOs that has, until now, impeded their ability to work together in order to craft objectives, establish budget guidelines, and develop metrics for measuring IT value and success. In short, with this book as a guide, business leaders will learn how to manage IT as they would any other functional business unit.
From inside Google Ventures, a unique five-day process for solving tough problems, proven at thousands of companies in mobile, e-commerce, healthcare, finance, and more. Entrepreneurs and leaders face big questions every day: What’s the most important place to focus your effort, and how do you start? What will your idea look like in real life? How many meetings and discussions does it take before you can be sure you have the right solution? Now there’s a surefire way to answer these important questions: the Design Sprint, created at Google by Jake Knapp. This method is like fast-forwarding into the future, so you can see how customers react before you invest all the time and expense of creating your new product, service, or campaign. In a Design Sprint, you take a small team, clear your schedules for a week, and rapidly progress from problem, to prototype, to tested solution using the step-by-step five-day process in this book. A practical guide to answering critical business questions, Sprint is a book for teams of any size, from small startups to Fortune 100s, from teachers to nonprofits. It can replace the old office defaults with a smarter, more respectful, and more effective way of solving problems that brings out the best contributions of everyone on the team—and helps you spend your time on work that really matters.
Part narrative, part business book; Architect + Entrepreneur is filled with contemporary, relevant, fresh tips and advice, from a seasoned professional architect building a new business. The guide advocates novel strategies and tools that merge entrepreneurship with the practice of architecture and interior design. The Problem:Embarking on a new business venture is intimidating; you have questions. But many of the resources available to help entrepreneur architects and interior designers start their design business lack timeliness and relevance. Most are geared toward building colossal firms like SOM and Gensler using outdated methods and old business models. If you're an individual or small team contemplating starting a design business, this is your field guide; crafted to inspire action. The Solution:Using the lean startup methodology to create a minimum viable product, the handbook encourages successive small wins that support a broader vision enabling one to, "think big, start small, and learn fast." It's a unique take on design practice viewed through the lens of entrepreneurship and is designed to answer the questions all new business owners face, from the rote to the existential. Questions about: - Startup costs - Business models (old and new) - Marriage of business and design - Mindset - Branding & naming (exercises and ideas) - Internet marketing strategies - Passive income ideas - Setting your fee - Taxes - Standard Operating Procedures (SOPs) - Securing the work - Client relations - Software - Billing rates - Contracts Building a business isn't a singular act; it's a series of small steps. Using the outline found in Architect + Entrepreneur you can start today. The chapters are organized to guide you from idea to action. Rather than write a business plan you'll be challenged to craft a brand and you'll sell it using new technologies. Follow the guide sequentially and you'll have both the tools and a profitable small business.
This is your hands-on guide to designing, building, and operating an API Marketplace to allow your organization to expose internal services and customer data securely for use by external developers. The book shows the mutual nature of a relationship in which organizations benefit from revenue and the reach of a new digital channel and third-party developers benefit from leveraging APIs to build unique applications. Providing open access is a regulatory requirement in some sectors, such as financial services, and this book helps you to build a platform to comply with regulatory requirements while at the same time encouraging and supporting use by external development teams. The book provides the blueprints for assembling teams and systems to build and support an API ecosystem. It offers insight into how the Marketplace can be constructed in a way to allow agility and flexibility to meet aggressive startup developer timelines while balancing established enterprise requirements of stability, reliability, and governance. The goal of this book is to provide engineering teams with a view of the operational requirements and how to meet and exceed these by establishing foundational elements at design time. An API Marketplace presents a unique challenge as organizations have to share internal capability and customer data with external developers. Security practices and industry standards are contrasted and discussed in this book. Practical approaches are provided to build and support a third-party developer ecosystem, manage sandbox environments hosting APIs of varying complexities, and cover monetization strategies that are yielding positive results to achieve self-sustainability. What You Will Learn Understand the motivation and objectives for an API economy Build key technical components of an API platform Comply with regulatory requirements such as Open Banking Secure APIs and customer data from external attack Deliver APIs quickly while satisfying governance requirements Get insight into a real-world API Marketplace implementation Who This Book Is For Solution architects, API product owners, delivery and development leads, and developers; anyone developing APIs for consumption by external business partners; API developers who want more insight into regulatory compliance
A single dramatic software failure can cost a company millions of dollars - but can be avoided with simple changes to design and architecture. This new edition of the best-selling industry standard shows you how to create systems that run longer, with fewer failures, and recover better when bad things happen. New coverage includes DevOps, microservices, and cloud-native architecture. Stability antipatterns have grown to include systemic problems in large-scale systems. This is a must-have pragmatic guide to engineering for production systems. If you're a software developer, and you don't want to get alerts every night for the rest of your life, help is here. With a combination of case studies about huge losses - lost revenue, lost reputation, lost time, lost opportunity - and practical, down-to-earth advice that was all gained through painful experience, this book helps you avoid the pitfalls that cost companies millions of dollars in downtime and reputation. Eighty percent of project life-cycle cost is in production, yet few books address this topic. This updated edition deals with the production of today's systems - larger, more complex, and heavily virtualized - and includes information on chaos engineering, the discipline of applying randomness and deliberate stress to reveal systematic problems. Build systems that survive the real world, avoid downtime, implement zero-downtime upgrades and continuous delivery, and make cloud-native applications resilient. Examine ways to architect, design, and build software - particularly distributed systems - that stands up to the typhoon winds of a flash mob, a Slashdotting, or a link on Reddit. Take a hard look at software that failed the test and find ways to make sure your software survives. To skip the pain and get the experience...get this book.
#1 NEW YORK TIMES BEST SELLER • At last, a book that shows you how to build—design—a life you can thrive in, at any age or stage • “Life has questions. They have answers.” —The New York Times Designers create worlds and solve problems using design thinking. Look around your office or home—at the tablet or smartphone you may be holding or the chair you are sitting in. Everything in our lives was designed by someone. And every design starts with a problem that a designer or team of designers seeks to solve. In this book, Bill Burnett and Dave Evans show us how design thinking can help us create a life that is both meaningful and fulfilling, regardless of who or where we are, what we do or have done for a living, or how young or old we are. The same design thinking responsible for amazing technology, products, and spaces can be used to design and build your career and your life, a life of fulfillment and joy, constantly creative and productive, one that always holds the possibility of surprise.
This book addresses the challenges facing information management (IM) and presents practical solution propositions. The first section describes six current trends and challenges to IM. The second section introduces a comprehensive model of integrated information management (IIM). The third section, using six practical examples, describes how selected concepts of IIM can be implemented. This book is built upon the fundamental premise of transferring successful management concepts from industrial production to IT management.
The software development ecosystem is constantly changing, providing a constant stream of new tools, frameworks, techniques, and paradigms. Over the past few years, incremental developments in core engineering practices for software development have created the foundations for rethinking how architecture changes over time, along with ways to protect important architectural characteristics as it evolves. This practical guide ties those parts together with a new way to think about architecture and time.
