The microservice architecture for cloud-based systems is extended to not only require each loosely coupled component to be independently deployable, but also to provide independent routing for each component. This supports canary deployments, green/blue deployments and roll-back. Both ad hoc and system integration test traffic can be directed to components before they are released to production traffic. Front-end code is included in this architecture by using server-side rendering of JS bundles. Environments for integration testing are created with preproduction deploys side by side with production deploys using appropriate levels of isolation. After a successful integration test run, preproduction components are known to work with production precisely as it is. For isolation, test traffic uses staging databases that are copied daily from the production databases, omitting sensitive data. Safety and security concerns are dealt with in a targeted fashion, not monolithically. This architecture scales well with organization size; is more effective for integration testing; and is better aligned with agile business practices than traditional approaches.
翻译:云基系统的微观服务架构扩展至不仅要求每个松散的组合组件独立可部署,而且为每个组件提供独立的路径。 这支持了金丝雀部署、绿色/蓝色部署和滚回。 临时和系统集成测试流量都可以在向生产流量释放之前直接针对部件。 将前端代码纳入这一架构, 使用服务器侧面的 JS捆绑图; 一体化测试环境由生产前与使用适当隔离水平的生产部署同时部署而创建。 在成功进行集成测试后, 预产组件将按原样生产。 对于孤立, 测试交通中转数据库, 每天从生产数据库复制, 省略敏感数据 。 安全和安保问题以有针对性的方式处理, 而不是单项处理 。 这一架构与组织规模相匹配; 整合测试更有效; 并且比传统方法更符合灵活的业务做法 。