SW Design: Enterprise Application Patterns for Xamarin.Forms

https://developer.xamarin.com/guides/xamarin-forms/enterprise-application-patterns/

PDF: https://aka.ms/xamarinpatternsebook

Quoting:
"Architectural guidance for developing adaptable, maintainable, and testable Xamarin.Forms enterprise applications

This eBook provides guidance on how to implement the Model-View-ViewModel (MVVM) pattern, dependency injection, navigation, validation, and configuration management, while maintaining loose coupling. In addition, there's also guidance on performing authentication and authorization with IdentityServer, accessing data from containerized microservices, and unit testing."

RESOURCE: Code Smells and more (Design Patterns, Anti-Patterns and Refactoring Tips)

One interesting reference guide to design patterns (and anti-patterns) as well as "code smells" (who happen when the code you're touching smells like a rotten bird in your garden) is: 

• https://sourcemaking.com/design_patterns (Design Patterns: structural and more; also remember to avoid anti-patterns)
• https://sourcemaking.com/refactoring (code smells: what to do to improve this "code smell"?)

Nice readings. 

BOOK: Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services (Robert Daigneau)

On patterns related to Web Services (SOAP and REST):

• http://www.amazon.com/Service-Design-Patterns-Fundamental-Solutions/dp/032154420X/ref=pd_sim_sbs_14_5?ie=UTF8&dpID=41A7b4McRzL&dpSrc=sims&preST=_AC_UL320_SR240%2C320_&refRID=1KKZFGSE9M8CEDJ03BNB 

Quoting:
"Web services have been used for many years. In this time, developers and architects have encountered a number of recurring design challenges related to their usage, and have learned that certain service design approaches work better than others to solve certain problems. (...)

This book will help readers answer the following questions:

• How do you create a web service API, what are the common API styles, and when should a particular style be used?
• How can clients and web services communicate, and what are the foundations for creating complex conversations in which multiple parties exchange data over extended periods of time?
• What are the options for implementing web service logic, and when should a particular approach be used?
• How can clients become less coupled to the underlying systems used by a service?
• How can information about a web service be discovered?
• How can generic functions like authentication, validation, caching, and logging be supported on the client or service?
• What changes to a service cause clients to break?
• What are the common ways to version a service? How can web services be designed to support the continuing evolution of business logic without forcing clients to constantly upgrade?"

BOOK: Patterns of Enterprise Application Architecture (Fowler)

For Enterprise Design Patterns this book is a must:

• http://www.amazon.com/Patterns-Enterprise-Application-Architecture-Martin/dp/0321127420/ref=pd_bxgy_14_img_3?ie=UTF8&refRID=03P48V22NYWE65KC0NV4

Citando:
"The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. (...)

The topics covered include

·  Dividing an enterprise application into layers
·  The major approaches to organizing business logic
·  An in-depth treatment of mapping between objects and relational databases
·  Using Model-View-Controller to organize a Web presentation
·  Handling concurrency for data that spans multiple transactions
·  Designing distributed object interfaces"

BOOK: Design Patterns: Elements of Reusable Object-Oriented Software (Gamma et al)

This is a must-read book aka as the Bible for Design Patterns written by the Gang of Four (GoF: Gamma et al.).

The main con is that examples are not in C# or Java (C++ and Smalltalk is used) but most of the design patterns introduced there are still widely used today.

Details here.