2026-09-19T01:47:16Zhttps://dspace.mit.edu/server/oai/request

oai:dspace.mit.edu:1721.1/1389762022-01-15T03:08:57Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023

Jackson, Daniel Ryabin, Aleks Talkar, Arman Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science 2022-01-14T14:42:15Z 2022-01-14T14:42:15Z 2021-06 2021-06-17T20:14:28.018Z https://hdl.handle.net/1721.1/138976 When developing a Software-as-a-Service (SaaS) product using a microservices architecture, there often exists a conflict between product stability, by virtue of testing, and agility/throughput, by virtue of being able to deploy independently and quickly. This thesis presents Flow, a pattern for microservice development that bridges this tradeoff. Using semantic versioning, explicit specification, and development/deployment time tooling, Flow provides reasonable assurance that deployed microservices will be compatible with one another without the need for time-consuming, comprehensive end-to-end tests. When combined with integration testing, Flow provides assurance of both the compatibility and functionality of deployed microservices. Flow’s key advantage over existing solutions is its extremely fast feedback loop that provides developers with compatibility information at compile-time, allowing development to be compatibility-aware. Flow is demonstrated using a visual model, a standalone artifact that simulates the state and enforcement rules that comprise the pattern. The model serves as a blueprint for the full-fledged tooling that would enforce the pattern in a production environment. M.Eng. Massachusetts Institute of Technology In Copyright - Educational Use Permitted Copyright MIT http://rightsstatements.org/page/InC-EDU/1.0/ Flow: a microservice architecture for achieving confidence in the compatibility of deployed microservices Thesis application/pdf Master Master of Engineering in Electrical Engineering and Computer Science Publication unknown unknown <Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="d2453eb4-1f7c-454b-b38a-8795a1b7c199"> <Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type> <Title>Flow: a microservice architecture for achieving confidence in the compatibility of deployed microservices</Title> <PublishedIn> <Publication> </Publication> </PublishedIn> <PublicationDate>2021-06</PublicationDate> <Authors> <Author> <DisplayName>Talkar, Arman</DisplayName> <Affiliation> <OrgUnit> </OrgUnit> </Affiliation> </Author> </Authors> <Editors> </Editors> <Publishers> <Publisher> <DisplayName>Massachusetts Institute of Technology</DisplayName> <OrgUnit /> </Publisher> </Publishers> <License>http://rightsstatements.org/page/InC-EDU/1.0/</License> <Abstract>When developing a Software-as-a-Service (SaaS) product using a microservices architecture, there often exists a conflict between product stability, by virtue of testing, and agility/throughput, by virtue of being able to deploy independently and quickly. This thesis presents Flow, a pattern for microservice development that bridges this tradeoff. Using semantic versioning, explicit specification, and development/deployment time tooling, Flow provides reasonable assurance that deployed microservices will be compatible with one another without the need for time-consuming, comprehensive end-to-end tests. When combined with integration testing, Flow provides assurance of both the compatibility and functionality of deployed microservices. Flow’s key advantage over existing solutions is its extremely fast feedback loop that provides developers with compatibility information at compile-time, allowing development to be compatibility-aware. Flow is demonstrated using a visual model, a standalone artifact that simulates the state and enforcement rules that comprise the pattern. The model serves as a blueprint for the full-fledged tooling that would enforce the pattern in a production environment.</Abstract> <Access xmlns="http://purl.org/coar/access_right" > </Access> </Publication>