At the beginning of this chapter, we said that there are many different patterns, guides, and sets of good practices published by different specialists, either from academic environments or from corporations.

They can be also applied to distinct programming contexts, and for different programming paradigms: the integration of applications, data management, user interfaces, application testing (unit or behavioral), and so on. They are usually called Domain Specific patterns.

In any case, as technology evolves, so do the patterns. New patterns appear, and some others become less used, just because the technology or architecture they apply to also falls into disuse.

Some others, in turn, get revitalized as the technology grows, such as in the case of Design and Implementation Guidelines for Web Clients, which you can find at https://msdn.microsoft.com/en-us/library/ff650462.aspx. However, if we consider other patterns very useful at the moment, such as Data patterns (https://msdn.microsoft.com/en-us/library/ff648420.aspx), chances are that you'll find them a little outdated just because it was published in 2003, and things have changed a lot since then, not to mention the appearance of other models and technologies, such as the Big Data revolution.

So, keep in mind the big principles first, and when you have to apply any of them for the sake of your application, take a look at the available patterns (classic or new) because they might offer you a trusted, proved solution.