This brings us to the end of our journey into the world of the Chef server API and search. We have learned about the authentication mechanisms used by Chef API and we have also seen various endpoints provided by Chef to perform actions across multiple resources. We have also learned about Ridley, one of the very few popular Chef API clients. We have also seen how you can use the power of search to find details about resources present on the Chef server. You can build pretty nice tools to use by using the Chef server API. We'll see some of these tools in later chapters. Search is perhaps one of the most beneficial features of the Chef server and this can be used either in a command line or in your recipes to gain a quick insight into your infrastructure or the Chef server itself. With this knowledge in hand, you can build a really robust and scalable infrastructure with a very high degree of automation.