Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Software Engineering with Golang

You're reading from   Hands-On Software Engineering with Golang Move beyond basic programming to design and build reliable software with clean code

Arrow left icon
Product type Paperback
Published in Jan 2020
Publisher Packt
ISBN-13 9781838554491
Length 640 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Achilleas Anagnostopoulos Achilleas Anagnostopoulos
Author Profile Icon Achilleas Anagnostopoulos
Achilleas Anagnostopoulos
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Section 1: Software Engineering and the Software Development Life Cycle
2. A Bird's-Eye View of Software Engineering FREE CHAPTER 3. Section 2: Best Practices for Maintainable and Testable Go Code
4. Best Practices for Writing Clean and Maintainable Go Code 5. Dependency Management 6. The Art of Testing 7. Section 3: Designing and Building a Multi-Tier System from Scratch
8. The Links 'R'; Us Project 9. Building a Persistence Layer 10. Data-Processing Pipelines 11. Graph-Based Data Processing 12. Communicating with the Outside World 13. Building, Packaging, and Deploying Software 14. Section 4: Scaling Out to Handle a Growing Number of Users
15. Splitting Monoliths into Microservices 16. Building Distributed Graph-Processing Systems 17. Metrics Collection and Visualization 18. Epilogue
19. Assessments 20. Other Books You May Enjoy

Chapter 12

  1. In a leader-follower configuration, the nodes hold an election and elect a leader for the cluster. All reads and writes go through the cluster leader, while the other nodes monitor the leader and automatically hold a new election if the leader becomes unavailable. As the name implies, in a multi-master configuration, the cluster has several master nodes and each of the master nodes can serve both read and write requests. The master nodes implement some form of distributed consensus algorithm (Raft, Paxos, and so on) to ensure that they always share the same view of the cluster's state.
  1. When implementing the checkpoint strategy, workers are periodically asked by the master to persist their current state to durable storage. If this operation succeeds, a new checkpoint is created. If a worker crashes or becomes unavailable, the master will request for the remaining...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime