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)

Summary

Microservices is an architectural style for building software applications that focuses on breaking down the application into a collection of small, independent services, each running in its own process and communicating over lightweight protocols.

Microservices architecture emphasizes the principle of “divide and conquer” by breaking down complex applications into smaller, manageable, and loosely coupled services. Each microservice represents a specific business capability or domain, and they can be developed, deployed, and scaled independently.

Microservices offer numerous advantages, including improved scalability, flexibility, maintainability, and faster development cycles. They allow for granular scaling, independent service updates, and better isolation of failures. They also have several defining characteristics, including single responsibility, independence, decentralized data management, and communication through APIs.

Service discovery and registration...