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 now! 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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Network Programming and Automation Essentials

You're reading from   Network Programming and Automation Essentials Get started in the realm of network automation using Python and Go

Arrow left icon
Product type Paperback
Published in Apr 2023
Publisher Packt
ISBN-13 9781803233666
Length 296 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Claus Töpke Claus Töpke
Author Profile Icon Claus Töpke
Claus Töpke
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Part 1: Foundations for Network Automation
2. Chapter 1: Network Basics for Development FREE CHAPTER 3. Chapter 2: Programmable Networks 4. Chapter 3: Accessing the Network 5. Chapter 4: Working with Network Configurations and Definitions 6. Part 2: Network Programming for Automation
7. Chapter 5: Dos and Don’ts for Network Programming 8. Chapter 6: Using Go and Python for Network Programming 9. Chapter 7: Error Handling and Logging 10. Chapter 8: Scaling Your Code 11. Part 3: Testing, Hands-On, and Going Forward
12. Chapter 9: Network Code Testing Framework 13. Chapter 10: Hands-On and Going Forward 14. Index 15. Other Books You May Enjoy

Using microservices and containers

When software is built based on a combination of small, independent services, we normally say the software was built using microservices architecture. Microservices architecture is a way to develop applications by combining small services that might belong or not to the same software development team.

The success of this approach is due to the isolation between each service, which is accomplished by using Linux containers (described in Chapter 2). Using Linux containers is a good way to isolate memory, CPU, networks, and disks. Each Linux container can’t interact with other Linux containers in the same host unless a pre-defined communication channel is established. The communication channels of a service have to use well-documented APIs.

The machine that runs microservices is normally called a container host or just a host. A host can have multiple microservices that may or may not communicate with each other. A combination of hosts is...

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