Book Image

Clean Code with C# - Second Edition

By : Jason Alls
4.5 (2)
Book Image

Clean Code with C# - Second Edition

4.5 (2)
By: Jason Alls

Overview of this book

Traditionally associated with Windows desktop applications and game development, C# has expanded into web, cloud, and mobile development. However, despite its extensive coding features, professionals often encounter issues with efficiency, scalability, and maintainability due to poor code. Clean Code in C# guides you in identifying and resolving these problems using coding best practices. This book starts by comparing good and bad code to emphasize the importance of coding standards, principles, and methodologies. It then covers code reviews, unit testing, and test-driven development, and addresses cross-cutting concerns. As you advance through the chapters, you’ll discover programming best practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. You’ll also explore API design and code quality enhancement tools, while studying examples of poor coding practices to understand what to avoid. By the end of this clean code book, you’ll have the developed the skills needed to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (18 chapters)

The design process for building successful microservices

Designing successful microservices involves careful planning, architecture, and development. Here is a step-by-step guide to the design process for building successful microservices:

  1. Identify business goals: Understand the business requirements and goals. Identify the functionalities that need to be broken down into separate services. Focus on the core competencies and domains that require microservices architecture.
  2. Decompose the monolith: If you are migrating from a monolithic architecture, analyze the existing application and identify modules that can be decoupled into independent services. These modules can be good candidates for microservices.
  3. Domain-driven design (DDD): Apply DDD principles to divide your system into bounded contexts, each representing a specific domain. These bounded contexts will be the foundation for defining your microservices.
  4. Service boundaries: Define clear boundaries for each...