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.

"With Kanban, every minute you spend on a software project can add value for customers. One book can help you achieve this goal: Agile Project Management with Kanban. Author Eric Brechner pioneered Kanban within the Xbox engineering team at Microsoft. Now he shows you exactly how to make it work for your team. Think of this book as {28}Kanban in a box.

A NEW YORK TIMES and WALL STREET JOURNAL bestseller 'A must read for entrepreneurs of all stripes' - Eric Ries, author of The Lean Startup From three partners at Google Ventures, a unique five-day process for solving tough business problems, proven at more than 100 companies. What’s the most important place to focus your effort? How many meetings and discussions does it take before you can be sure you have the right solution? What will your idea look like in real life? How do you start? Now there’s a surefire way to answer these important questions: the sprint. Designer Jake Knapp created the five-day process at Google, where sprints were used on everything from Google Search to Google X. He joined Braden Kowitz and John Zeratsky at Google Ventures, and together they have completed more than one hundred sprints with companies in mobile, e-commerce, healthcare, finance, and more. 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’s for anyone with a big opportunity, problem, or idea who needs to get answers today.

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