Abstract The term "Microservice Architecture" has sprung up over the last few years to describe a 'particular' way of designing software applications. Like every new industry FADSynonym for SOA, BPEL, WADL, etc, including but not limited to Service Oriented Architecture (SOA), Microservices architecture has no precise definition, and it follows the “it depends” school of ivory tower software design. Following this prevalent and ubiquitous architectural style, we introduce a novel architectural design pattern called (pico) p-Services Architecture. Our architectural pattern addresses the prevelant characteristics around organizations such as maintaining and increasing technical debt, forming silos to decrease business capability, not leveraging automated deployment, ensuring lack of intelligence in the endpoints, and centralizedReviewer 2 thinks bottle neck sounds too pejoritive. control of languages and data. Following are the tenets of the pico services architecture to help redirect focus away from the minor problems in enterprise distributed computing such as compliance, security, scalability, and fragmentation.