Recently, I want to read the net distributed applications book and take study notes. I systematically studied distributed application development and design.

A few days ago, I browsed it roughly. It was quite good. It made me understand what a real distributed architecture is and what I used before.ProgramLayering is not the same thing. I used to write a "standalone version" program, so I don't feel the benefits of layering. The original layering came from distributed...

This book introduces the following knowledge points:

• Component Technology and classification (divided into service providers and information packages)
• XML Service
• . NET Enterprise Service (actually COM +)
• Multithreading
• Windows Service
• MSMQ (Message Queue)
• . Net remoting

 

It also describes in detail what to consider when designing a distributed system:

• Data Layer Optimization
• Security
• Monitoring
• Logs
• Performance Tracking and counters
• Upgrade deployment policy

 

Finally, we will introduce three case projects step by step to help readers better understand the use of these technologies.

A bad thing is that this book is based on. NET 1.1. It seems a little outdated, but its design and philosophy are also worth learning.

I plan to finish reading the book in one month, and finish the exercises and case programs. After reading the book, I plan to read the next book:

Enterprise Services with the. NET Framework: developing distributed business solutions with. NET Enterprise Services (Microsoft. NET development series)