{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,10,5]],"date-time":"2025-10-05T16:58:09Z","timestamp":1759683489542,"version":"3.41.0"},"reference-count":7,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[2016,5,1]],"date-time":"2016-05-01T00:00:00Z","timestamp":1462060800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2016,5]]},"abstract":"<jats:p>Microservices are an approach to building distributed systems in which services are exposed only through hardened APIs; the services themselves have a high degree of internal cohesion around a specific and well-bounded context or area of responsibility, and the coupling between them is loose. Such services are typically simple, yet they can be composed into very rich and elaborate applications. The effort required to adopt a microservices-based approach is considerable, particularly in cases that involve migration from more monolithic architectures. The explicit benefits of microservices are well known and numerous, however, and can include increased agility, resilience, scalability, and developer productivity. This article identifies some of the hidden dividends of microservices that implementers should make a conscious effort to reap.<\/jats:p>","DOI":"10.1145\/2956641.2956643","type":"journal-article","created":{"date-parts":[[2016,6,15]],"date-time":"2016-06-15T19:32:01Z","timestamp":1466019121000},"page":"25-34","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":12,"title":["The Hidden Dividends of Microservices"],"prefix":"10.1145","volume":"14","author":[{"given":"Tom","family":"Killalea","sequence":"first","affiliation":[]}],"member":"320","published-online":{"date-parts":[[2016,5]]},"reference":[{"key":"e_1_2_1_1_1","volume-title":"Permissionless innovation. IETF","author":"Arkko J.","year":"2013","unstructured":"Arkko , J. 2013. Permissionless innovation. IETF ; https:\/\/www.ietf.org\/blog\/ 2013 \/05\/permissionless-innovation\/. Arkko, J. 2013. Permissionless innovation. IETF; https:\/\/www.ietf.org\/blog\/2013\/05\/permissionless-innovation\/."},{"key":"e_1_2_1_2_1","unstructured":"Conway M. E. 1968. How do committees invent? Datamation Magazine; http:\/\/www.melconway.com\/Home\/Committees_Paper.html.  Conway M. E. 1968. How do committees invent? Datamation Magazine; http:\/\/www.melconway.com\/Home\/Committees_Paper.html."},{"key":"e_1_2_1_3_1","doi-asserted-by":"publisher","DOI":"10.1145\/1142055.1142065"},{"key":"e_1_2_1_4_1","unstructured":"Honest Status Page. 2015. @honest_update; https:\/\/twitter.com\/honest_update\/status\/651897353889259520.  Honest Status Page. 2015. @honest_update; https:\/\/twitter.com\/honest_update\/status\/651897353889259520."},{"key":"e_1_2_1_5_1","volume-title":"The single responsibility principle","author":"Martin R. C.","year":"2014","unstructured":"Martin , R. C. 2014. The single responsibility principle ; http:\/\/blog.8thlight.com\/uncle-bob\/ 2014 \/05\/08\/SingleReponsibilityPrinciple.html. Martin, R. C. 2014. The single responsibility principle; http:\/\/blog.8thlight.com\/uncle-bob\/2014\/05\/08\/SingleReponsibilityPrinciple.html."},{"key":"e_1_2_1_6_1","volume-title":"The crypto warrior. Politico","author":"Perera D.","year":"2015","unstructured":"Perera , D. 2015. The crypto warrior. Politico ; http:\/\/www.politico.com\/agenda\/story\/ 2015 \/12\/crypto-war-cyber-security-encryption-000334. Perera, D. 2015. The crypto warrior. Politico; http:\/\/www.politico.com\/agenda\/story\/2015\/12\/crypto-war-cyber-security-encryption-000334."},{"key":"e_1_2_1_7_1","unstructured":"Yelp service principles; https:\/\/github.com\/Yelp\/service-principles.  Yelp service principles; https:\/\/github.com\/Yelp\/service-principles."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2956641.2956643","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/2956641.2956643","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T03:39:43Z","timestamp":1750217983000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2956641.2956643"}},"subtitle":["Microservices aren\u2019t for every company, and the journey isn\u2019t easy."],"short-title":[],"issued":{"date-parts":[[2016,5]]},"references-count":7,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2016,5]]}},"alternative-id":["10.1145\/2956641.2956643"],"URL":"https:\/\/doi.org\/10.1145\/2956641.2956643","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2016,5]]},"assertion":[{"value":"2016-05-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}