#IstioCon Secure your microservices with istio step by step JianFeng Ding, LuYao Zhong #IstioCon Agenda ● Istio identity ● mTLS in Isito ● Secure ingress traffic ● Authorize ingress traffic ● Authorize Enable Access Control to your services via Istio authorization policy Istio will Secure your microservices for you! #IstioCon Thank you!

Leveraging Istio for Creating API Tests Low Effort API Testing for Microservices | CONFIDENTIAL • What has changed? – Migration to microservices triggering need for extensive API tests • Problem: – Creating auto-generated from end-to-end tests – Significantly reduced time and cost for API testing for microservices architectures with Istio – Fewer failures higher up the test pyramid as a result of improved

master's degree in computer science from Columbia University. Title : Behavior-driven Tests for Microservices-based Algo Trading System Summary : Introduction : This poster will introduce a test framework framework we use at Bloomberg to enable behavior-based tests in natural language style for a microservices-based algo trading system that our engineering team is responsible for. Relevance : For our

Date: 2019-09-20 Security Level: Contents 1. Tool for Splitting Monolithic Applications into Microservices 2. Contract Management Tool 3 Advantages of the Microservice Architecture Factor Monolithic Major Difficulty in Building the Microservice Architecture: How to Split an Application into Microservices? • Factors > Team size > Delivery cycle > Business direction > Fault scope > Data scale > Throughput technology: application-level formal verification Tool for Splitting Monolithic Applications into Microservices Improves Development Efficiency Supported processes Methodology • ThoughtWorks 5 Steps and

22 1. Fork and clone the repositories: microservices-demo and front-end You will need a GitHub account for this step. Before you can modify the microservices demo application, The Sock Shop, fork the https://github.com/microservices-demo/front-end - This is the front-end service of the Sock Shop application. You will update the color the buttons in this example. • https://github.com/microservices-demo/microservices-demo Container Image Using an editor of your choice, open manifests/front-end-dep.yaml, from the microservices-demo repo you forked and update the image line. Change it from: image: weaveworksdemos/front-end

ServiceComb-based Microservice Practice of MedSci Miao Yanjie Chief Architect, MedSci Service Mesh-based Microservices and Those Based on a Traditional Architecture Two network platforms, covering all users in improving report processing efficiency by more than 80% by using new technologies such as microservices and AI. iDrugSafety Competitiveness Analysis Quality Cost Specifications System Functions evolved. • Multiple languages are supported. The hybrid deployment of Service Mesh-based microservices and those bases on a traditional architecture is supported. • There are many successful commercial

system configurations through easy-to-understand data and portals. Develops and deploys microservices in the same domain using multiple programming languages. Enables collaboration and governance quickly build microservice projects based on popular microservices frameworks and popular programming models, reducing the cost of microservices entry, enabling users to focus on business development 验收微服务 Collaboratively implement standard management of contract-based data and services Divide microservices (including dependencies) Define contract (interface and model) Release contract Microservice

Grab-Kit (GK) 02. Local Development WHAT Grab-Kit, an RPC framework for microservices, creates skeleton microservices and generates boilerplate code from API definitions. WHY • Save time & effort Land the code into master CI/CD 第三部分 CI/CD 03. Grab’s CI/CD system Microservices created over time Go monorepo & microservices (2017-2021) 03. Grab’s CI/CD system 4 Years later… 03. Grab’s CI/CD CI/CD system 60 PRODUCTION DEPLOYMENTS / DAY 225K INTEGRATION TESTS / DAY 600 MICROSERVICES 140 COMMITS / WORKING DAYS 1,000 ACTIVE CONTRIBUTORS 210K TOTAL COMMITS 272 STAGING

referred to as microservices, wherein a large applica�on is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP. Microservices applica�ons delivery. This shi� toward highly dynamic microservices presents both a challenge and an opportunity in terms of securing connec�vity between microservices. Tradi�onal Linux network security approaches iptables) filter on IP address and TCP/UDP ports, but IP addresses frequently churn in dynamic microservices environments. The highly vola�le life cycle of containers causes these approaches to struggle

referred to as microservices, wherein a large application is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP. Microservices applications delivery. This shift toward highly dynamic microservices presents both a challenge and an opportunity in terms of securing connectivity between microservices. Traditional Linux network security approaches iptables) filter on IP address and TCP/UDP ports, but IP addresses frequently churn in dynamic microservices environments. The highly volatile life cycle of containers causes these approaches to struggle