Downloaded 57 times
![T E R M I N A L
$ curl http://localhost:8500/v1/catalog/service/redis
[
{
"ID": "52f73400-a352-80d2-9624-e70cc9996762",
"Node": "consul-client-2",
"Address": "10.0.1.83",
"Datacenter": "dc1",
"ServiceName": "redis",
"ServiceTags": [
"global",
"cache"
],
"ServiceAddress": "10.0.1.83",
"ServicePort": 24815,
"ModifyIndex": 31,
…](https://image.slidesharecdn.com/consulconnect-181003145143/85/Consul-Service-Mesh-for-Microservices-35-320.jpg)
![{
"service": "web",
"connect": {
"proxy": {
"config": {
"upstreams": [{
"destination_name": "redis",
"local_bind_port": 1234
}]
}
}
}
}
C O D E E D I T O R](https://image.slidesharecdn.com/consulconnect-181003145143/85/Consul-Service-Mesh-for-Microservices-55-320.jpg)
More Related Content
Similar to Consul: Service Mesh for Microservices
Consul: Service Mesh for Microservices
- 1. Service Mesh forMicroservices
- 2. Armon Dadgar Founder andCTO @armon
- 3. PROVISION, SECURE ANDRUN ANY INFRASTRUCTURE Nomad Consul Vault Vagrant Packer Terraform Consul Enterprise Terraform Enterprise Vault Enterprise PRODUCT SUITEOSS TOOL SUITE RUN Applications SECURE Application Infrastructure PROVISION Infrastructure FOR INDIVIDUALS FOR TEAMS Nomad Enterprise
- 4. Service Mesh forMicroservices
- 5.
- 6.
- 7.
- 8.
- 9. Zone FirewallDMZ Firewall Monolith AB C D Static IP LB
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16. Operating in theCloud + Containers Dynamic IP Addresses Higher Failure Rate Ephemeral Infrastructure Complex Network Topology
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23. Defining Segmentation Splitting networkinto sub-networks Restricting communication between sub-networks Virtual LAN, Firewalls, Software Defined Networks Coarse Grained, Many Services Segment A Segment B Network
- 24. Zone FirewallDMZ Firewall Monolith AB C D Static IP LB
- 25.
- 27. A -> B C-> D D -> C A B C D
- 28. B -> DA-> C A B C D
- 30. Service Mesh forMicroservices Service Discovery. Connect services with a dynamic registry Service Configuration. Configure services with runtime configs Service Segmentation. Secure services based on identity
- 31. Consul Usage Launched in2014 12K+ GitHub Stars 1M+ Downloads monthly Customers running 50,000+ agents
- 32.
- 33. Service Discovery Registry ofNodes, Services, Checks DNS API HTTP API Web UI
- 34. T E RM I N A L $ dig redis.service.consul ; <<>> DiG 9.8.3-P1 <<>> redis.service.consul ; (3 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9046 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;redis.service.consul.IN A ;; ANSWER SECTION: redis.service.consul. 0 IN A 10.1.10.38
- 35. T E RM I N A L $ curl http://localhost:8500/v1/catalog/service/redis [ { "ID": "52f73400-a352-80d2-9624-e70cc9996762", "Node": "consul-client-2", "Address": "10.0.1.83", "Datacenter": "dc1", "ServiceName": "redis", "ServiceTags": [ "global", "cache" ], "ServiceAddress": "10.0.1.83", "ServicePort": 24815, "ModifyIndex": 31, …
- 37. Service Configuration Hierarchical Key/ValueStore HTTP API Long-polling / Edge trigger Locking
- 38. T E RM I N A L $ consul kv put service/web/enable_foo true Put successfully! $ consul kv get service/web/enable_foo true
- 40.
- 41. Consul Connect Service AccessGraph Certificate Distribution Application Integration
- 42. Service Access Graph Intentionsto Allow/Deny Communication Source and Destination Service Scale Independent Managed with CLI, API, UI, Terraform
- 43. T E RM I N A L $ consul intention create -deny web '*' Created: web => * (deny) $ consul intention create -allow web db Created: web => db (allow)
- 45. Certificate Distribution Transport LayerSecurity (TLS) Service Identity Encryption of all traffic
- 46. Certificate Generation Automatic Generation& Rotation ServerClient Certificate Signing Request Generate Key Pair Sign Certificate
- 47.
- 48.
- 49.
- 50. Certificate Authority Rotation Root Intermediary Leaf Root IntermediaryIntermediary Leaf Leaf
- 51. Application Integration Consul Clientfor Service Graph and Certificates Sidecar Proxies Native Integrations
- 52. Sidecar Proxy Integration NoCode Modification Minimal Performance Overhead Operational Flexibility
- 53.
- 54.
- 55. { "service": "web", "connect": { "proxy":{ "config": { "upstreams": [{ "destination_name": "redis", "local_bind_port": 1234 }] } } } } C O D E E D I T O R
- 56.
- 57. T E RM I N A L $ consul connect proxy -service web -upstream postgresql:8181 $ psql -h 127.0.0.1 -p 8181 -U mitchellh mydb >
- 58. Native Integration Standard TLS NegligiblePerformance Overhead Requires Code Modification
- 59. // Create aConsul API client client, _ := api.NewClient(api.DefaultConfig()) // Create an instance representing this service. svc, _ := connect.NewService("my-service", client) defer svc.Close() // Creating an HTTP server that serves via Connect server := &http.Server{ Addr: ":8080", TLSConfig: svc.ServerTLSConfig(), // ... other standard fields } // Serve! server.ListenAndServeTLS("", "") C O D E E D I T O R
- 60. Consul Connect Service AccessGraph. Intentions allow or deny communication of logical services. Certificate Distribution. Standard TLS certificates with SPIFFE compatibility. Application Integration. Native integrations or side car proxies.
- 61.
- 62. Deployment Single Binary Server andClient Agents 3-5 Servers per Datacenter Multi-Datacenter Support
- 63. Consul Servers Replicated State,Automatic Failover Service Registry Service Access Graph Key/Value Store Multi-DC Forwarding Leader FollowerFollower Replication
- 64. Consul Clients Expose HTTPand DNS API Transparently Forward Register and Monitor Services Cache Service Graph Server(s) Client
- 65. Cluster Awareness Lightweight Gossip(Serf) Cluster Membership Failure Detection Gossip Server Client Client
- 66. Cluster Membership Join RequiresAny Peer Server Discovery Protocol Versioning New Server Server Client Client Server
- 67. Failure Detection Leaving vsFailing Automatic Reaping No Heart beating Failed Client Server Client Client
- 68.
- 69.
- 70. Control Plane vs.Data Plane Consul as Control Plane Pluggable Proxies as Data Plane Configure Communicate Control Data Data
- 71.
- 72. Consul with Containers ConsulAgent per Host DaemonSet with Kubernetes Proxy per Container / Pod
- 73. Consul Architecture Batteries Included HighlyAvailable & Scalable Pluggable Data Plane
- 74.
- 75. Common Challenges Infrastructure ismeans to an ends Microservices Architecture Operational Challenges
- 76. Patchwork Solutions Re-invent thewheel Long Term Maintenance Minimum Viable vs Maximum Utility
- 77. Service Mesh forMicroservices Service Discovery. Connect services with a dynamic registry Service Configuration. Configure services with runtime configs Service Segmentation. Secure services based on identity