https://s3-us-west-2.amazonaws.com/secure.notion-static.com/b82577ec-2c05-49c6-a878-fd2531d16ae1/2019181422.jpeg

A Philosophy of Software Design John Ousterhout

This book addresses the topic of software design: how to decompose complex software systems into modules (such as classes and methods) that can be implemented relatively independently. The book first introduces the fundamental problem in software design, which is managing complexity. It then discusses philosophical issues about how to approach the software design process, and it presents a collection of design principles to apply during software design. The book also introduces a set of red flags that identify design problems.

You can apply the ideas in this book to minimize the complexity of large software systems, so that you can write software more quickly and cheaply.


https://s3-us-west-2.amazonaws.com/secure.notion-static.com/9f72cb54-2a96-46e3-b432-7ce3ce8f7a6b/1227901087.jpeg

Agile Application Security: Enabling Security in a Continuous Delivery Pipeline Laura Bell, Michael Brunton-Spall, Rich Smith, Jim Bird

Agile continues to be the most adopted software development methodology among organizations worldwide, but it generally hasn't integrated well with traditional security management techniques. And most security professionals aren’t up to speed in their understanding and experience of agile development. To help bridge the divide between these two worlds, this practical guide introduces several security tools and techniques adapted specifically to integrate with agile development.

Written by security experts and agile veterans, this book begins by introducing security principles to agile practitioners, and agile principles to security practitioners. The authors also reveal problems they encountered in their own experiences with agile security, and how they worked to solve them.


https://s3-us-west-2.amazonaws.com/secure.notion-static.com/79cdbde8-c04c-47bb-b8d3-038bd7bbb056/61kAECouJL.jpg

Building Evolutionary Architectures: Support Constant Change Neal Ford, Rebecca Parsons. Patrick Kua

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.


https://s3-us-west-2.amazonaws.com/secure.notion-static.com/da420cff-9880-49c8-9312-f017a701970c/513CEhKoGYL._SX379_BO1204203200_.jpg

Building Microservices: Designing Fine-Grained Systems (2nd Edition) Sam Newman

Distributed systems have become more fine-grained in the past 10 years, shifting from code-heavy monolithic applications to smaller, self-contained microservices. But developing these systems brings its own set of headaches. With lots of examples and practical advice, the second edition of this practical book takes a holistic view of the topics that system architects and administrators must consider when building, managing, and evolving microservice architectures.

Microservice technologies are moving quickly, and this revised edition gets you up to date with a new chapter on serverless and cloud-native applications, expanded coverage of user interfaces, more hands-on code examples, and other additions throughout the book.

Author Sam Newman provides you with a firm grounding in the concepts while diving into current solutions for modeling, integrating, testing, deploying, and monitoring your own autonomous services. You’ll follow a fictional company throughout the book to learn how building a microservice architecture affects a single domain


https://s3-us-west-2.amazonaws.com/secure.notion-static.com/3b9dadd5-74f2-44ac-b83c-e4dafdf72421/unnamed.png

Building Secure & Reliable Systems [FREE!] Google SRE Team

Can a system be considered truly reliable if it isn't fundamentally secure? Or can it be considered secure if it's unreliable? Security is crucial to the design and operation of scalable systems in production, as it plays an important part in product quality, performance, and availability. In this book, experts from Google share best practices to help your organization design scalable and reliable systems that are fundamentally secure.

Two previous O'Reilly books from Google--Site Reliability Engineering and The Site Reliability Workbook--demonstrated how and why a commitment to the entire service lifecycle enables organizations to successfully build, deploy, monitor, and maintain software systems. In this latest guide, the authors offer insights into system design, implementation, and maintenance from practitioners who specialize in security and reliability. They also discuss how building and adopting their recommended best practices requires a culture that's supportive of such change.