Update README.md

Added service locator information

README.md

@@ -21,6 +21,7 @@
 	* [Facade](#facade)
 	* [Flyweight](#flyweight)
 	* [Proxy](#proxy)
+	* [Service Locator](#service-locator)
 * Behavioral Patterns
 	* [Chain of responsibility](#chain-of-responsibility)
 	* [Command](#command)
@@ -174,6 +175,19 @@
 * facilitate network connection
 * to count references to an object
 
+## <a name="service-locator">Service Locator</a> [&#8593;](#list-of-design-patterns)
+**Intent:** Encapsulate the processes involved in obtaining a service with a strong abstraction layer.
+
+![alt text](https://github.com/iluwatar/java-design-patterns/blob/master/service-locator/etc/service-locator.png "Proxy")
+
+**Applicability:** The service locator pattern is applicable whenever we want to locate/fetch various services using JNDI which, typically, is a redundant and expensive lookup. The service Locator pattern addresses this expensicve lookup by making use of caching techniques ie. for the very first time a particular service is requested, the service Locator looks up in JNDI, fetched the relavant service and then finally caches this service object. Now, further lookups of the same service via Service Locator is done in its cache which improves the performance of application to great extent.
+
+
+**Typical Use Case:**
+
+* When network hits are expesive and time consuming
+* lookups of services are done quite frequently
+* large number of services are being used
 
 ## <a name="chain-of-responsibility">Chain of responsibility</a> [&#8593;](#list-of-design-patterns)
 **Intent:** Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.