In the many discussions and architecture approaches I’m reading about Micro-Services, a key point seems to elude the conversation. Namely, “What’s a Micro-Service?” Not what are the technical properties of a micro-service, but rather what level of BUSINESS functionality should be encapsulated in a single service, a single “micro” service? One “formal” definition that’s floating around is this… ...an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. - James Lewis and Martin Fowler via http://techbeacon.com/ From the SOA (service oriented architecture)
Enough hype! Real ROI - Let's put these technologies to work!