Distributed Applications with GO: Difference between revisions
Jump to navigation
Jump to search
| Line 24: | Line 24: | ||
*Transports | *Transports | ||
*Protocol | *Protocol | ||
==Sample App== | |||
The sample app is a hybrid app using GO | |||
<br> | |||
[[File:GO Demo Distributed App.png]] | |||
Revision as of 05:58, 23 August 2021
Elements of a Distributed System
Characteristic
Four aspects might be
- Service Discovery
- Load Balancing
- Distributed tracing and logging
- Service Monitoring
Type of Distributed System
- Hub and Spoke (Satélite approach)
- Advantages Good for load balancing and logging
- Disadvantages Bad to single point of failure. Hub is complex due to responsibilities
- Peer to Peer where each communicate directly
- Advantages No Single point of failure. Highly decoupled
- Disadvantages Service discovery and Load Balancing hard
- Message Queue System where services get work from the queue
- Advantages Easy to scale, Persistence for disaster
- Disadvantages Single Point of failure (message queue), hard to configure
- Hybrid system (none of the above)
- This might will have advantages and disadvantage of both
Architectural Element
These are the aspect you may want to consider
- Languages
- Frameworks
- Transports
- Protocol
Sample App
The sample app is a hybrid app using GO
