Here is a architecture ref. talking about building microservices app. with EAP 6, along with a detailed example:
(hit the "Download" button on right hand side)
>> I heard of docker, which i have never tried, should i really have to use docker for micro service pattern or is it possible with out it.
It is totally up to you (your actual requirement / design) whether to adopt Docker or not. It is a way of doing virtualization but you don't necessarily have to use Docker to build up your environment.
As in the ref. :
General characteristics of microservices include:
• Applications are developed as a suite of small services, each running as an independent process in its own logical machine1 (or Linux container)
• Services are built around capabilities2 : single responsibility principle
• One can independently replace / upgrade / scale / deploy services
• Standard lightweight communication is used, often REST calls over HTTP
• Potentially heterogeneous environments are supported
Virtualization reduces the overhead cost of each logical machine by sharing host resources and is often an acceptable environment for microservices. However, Linux containers and Docker technology in particular have improved on the benefits of virtualization by avoiding the full cost of an operating system and sharing some of host services that would be unnecessarily duplicated in each virtual machine. Docker containers are emerging as the preferred units of deployment for microservices.
Some more examples you can check how to build microservices with JBoss (EAP) and Docker
(Watch the video of that "Virtual JBUG" at bottom of this article, hand-on demo starts from 23:50)
Also this one