Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Microservices with Go

You're reading from   Microservices with Go The expert's guide to building secure, scalable, and reliable microservices with Go

Arrow left icon
Product type Paperback
Published in Jun 2025
Publisher Packt
ISBN-13 9781836207337
Length 428 pages
Edition 2nd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Alexander Shuiskov Alexander Shuiskov
Author Profile Icon Alexander Shuiskov
Alexander Shuiskov
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Introduction
2. Introduction to Microservices FREE CHAPTER 3. Foundation
4. Scaffolding a Go Microservice 5. Service Discovery 6. Serialization 7. Synchronous Communication 8. Asynchronous Communication 9. Storing Service Data 10. Setting Up Service Deployments 11. Unit and Integration Testing 12. Security and Compliance 13. Maintenance
14. Reliability Overview 15. Collecting Service Telemetry Data 16. Setting Up Service Alerting 17. Performance Monitoring 18. Advanced Topics
19. Implementing Distributed System Scenarios 20. Advanced Topics 21. Other Books You May Enjoy
22. Index

Asynchronous communication best practices

In this section, we are going to cover the best practices of using the asynchronous communication model. You will learn about some high-level recommendations for adopting the model in your applications and using it in a way that would maximize its benefits for you.

Versioning

Versioning is the technique of associating the format (or a schema) of the data with its version. Imagine you are working on a rating service, and you use a publisher-subscriber model for producing and consuming rating events. If at some point the format of your rating events gets changed, some of the events that are already being produced will have an old data format, and some will have the new one. This situation may be hard to handle because the logic consuming such data would need to know how to differentiate between such formats and how to handle each one. Differentiating between two formats without knowing the data schema or its version could be a nontrivial...

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
Visually different images