This document discusses microservices and how JBoss EAP and OpenShift can help implement them. It notes that microservices help define architecture, allow independent release cycles, and accelerate business velocity. Each microservice should do one thing well with well-defined inputs and outputs. This leads to loosely coupled implementations and locations. The document recommends that a bounded context, or microservice, should solve a problem that less than 8 people could handle. It provides examples of microservices for a conference application. JBoss EAP and WildFly Swarm can help implement microservices by wrapping servers around individual services while still providing capabilities like JAX-RS, CDI, JMS and more.