There is a lot of talk now around the term Service Mesh. The hype is high and the promise is real. The problem is that there is not really a good definition of what service mesh really is. In this talk we are going to review the problem service meshes are trying to solve, name the core components that make up a service mesh, and discuss the benefits an organization can receive by implementing this new technology.
%+27788225528 love spells in Boston Psychic Readings, Attraction spells,Bring...
Demystifying Service Mesh
1.
2.
3.
4. Back in the days – Client / Server
• Single application per Server
• No app mobility
• Security mapped to IP
• Seldom horizontal scale of an
app
• Few / None Load Balancers
5. Back in the days – Client / Server
• Single application per Server
• No app mobility
• Security mapped to IP
• Seldom horizontal scale of an
app
• Few / None Load Balancers
11. What if there was no IP?
▪ How would services find each other?
▪ How would services be able to securely connect to each to each other?
▪ How can you do traffic shaping based on strategies, updates or
failures?
18. Web-App Order Processing
xxx.xxx.xxx.153
Load Balancer VIP
xxx.xxx.xxx.163
Load Balancer VIP
DNS Entries
Web-app.internal.mycompany > xxx.xxx.xxx.153
Order-process.internal.mycompany > xxx.xxx.xxx.163
19. Web-App
xxx.xxx.xxx.153
Load Balancer VIP
▪ Ensure request balancing
▪ Handle circuit breaking
▪ Allow traffic to be routed to healthy nodes
▪ Abstract instance IP from service IP
24. Web-App Order Processing
xxx.xxx.xxx.153
Load Balancer VIP
xxx.xxx.xxx.163
Load Balancer VIP
Order-History
App Team Network Team
Deployed
Traffic Pattern Configured
xxx.xxx.xxx.173
Load Balancer VIP
Mobile-Access
25. Web-App Order Processing
Mobile-Access
Federated Link
Order-History
App Team
Deployed
Traffic Pattern Configured
web-app.service.consul order-history.service.consul order-processing.service.consul
mobile-access.service.consul
26. Example
# dig @127.0.0.1 -p 8600 -t SRV web.service.consul
;; ANSWER SECTION:
Web.service.consul. 0 IN SRV 1 1 80 consul-dc1-srv2.node.dc1.consul.
Web.service.consul. 0 IN SRV 1 1 80 consul-dc1-srv1.node.dc1.consul.
Web.service.consul. 0 IN SRV 1 1 80 consul-dc1-srv3.node.dc1.consul.
;; ADDITIONAL SECTION:
consul-dc1-srv2.node.dc1.consul. 0 IN A 192.168.43.102
consul-dc1-srv2.node.dc1.consul. 0 IN TXT "consul-network-segment="
consul-dc1-srv1.node.dc1.consul. 0 IN A 192.168.43.101
consul-dc1-srv1.node.dc1.consul. 0 IN TXT "consul-network-segment="
consul-dc1-srv3.node.dc1.consul. 0 IN A 192.168.43.103
consul-dc1-srv3.node.dc1.consul. 0 IN TXT "consul-network-segment="
Consul Service Discovery
50. Web-App Web-App Web-App
Development Testing Production
localhost localhost localhost
App Team
Cloud Team
Firewall Team
Network Team
▪ Environment configuration
▪ Secure Access Controls
▪ Network Optimization
51.
52. Takeaways
▪ To do service mesh right you need to start with the right premise : NO IP
▪ Service discovery is table stakes in this shift. This is a non-negotiable
▪ Have to measure ideas based on Agility, Portability, and Resiliency
▪ Consul is awesome … go check it out