MicroServices #3:
Make it easy!
References
The Twelve-Factor App
AWS Api Gateway
Heroku Foreman
Scenario...
(demo)
Ship It!
Encryption
Authentication
Tracking stats
Service dependencies
Configuration
Scaling
Load balancing
Request throttling
Firewall rules
Caching
Secret storage
And more?
7.1.4
ZeroMQ
Reliable Messaging
Encryption, Authentication, Streaming
Discovery, Scaling, Load Balancing
Building on Consul
Lots of libraries
Point-to-point messaging
Encryption, Auth, Fault tolerance in each service
7.2.0
The trouble with libraries...
More services = more touchpoints
More languages = more implementations
What about code we don't own?
New 7.2.0 Objectives
Performance
Install & Config experience
Scalability & Stability
Solve a hard problem once.
Process Manager
Api Gateway
No ZeroMQ
Process Manager
Consul registration
Vitals
Throttled Restart
OS-specific
Service management
Automatic startup
API Gateway
Runs on every host
Listens on a known port
Routes requests to services:
https://localhost:8501/lr-case-api/...
All Together Now
localhost:8501
localhost:8501
?
?
?
?
?
?
?
(demo)
What's next?
Made with Slides.com