Google Microservices Demo

Google Microservices Demo

And my fork - Microservices Demo - this is where all code from the articles is.

It gives you a good picture of how Docker and various technologies are used in production, as well as it allows simulating incidents and predictable learning.

This repository has multiple services in it. It’s not always the case. In many instances, you find a pattern “repository-per-project”. There are pros and cons to both. However, DevOps best practices are equal for both.

You can ignore almost anything for now except ./src folder. You can open this repository in your Visual Studio Code and navigate there. You’d find multiple nested folders there.

  • adservice written in Java
  • cartservice written in C# with Redis database
  • checkoutservice written in Go
  • currencyservice written in NodeJS
  • emailservice written in Python
  • frontend written in Go
  • loadgenerator it’s synthetic test written in Python using Locust framework
  • paymentservice written in NodeJS
  • productcatalogservice written in Go
  • recommendationservice written in Python
  • shippingservice written in Go

Key Considerations

This is a great learning repository because you learn how to build and work with multiple programming languages and platforms.

However, in the real world, having a “go-to” technology stack for maintainability is more common (it’s much easier to maintain multiple projects written using a single programming language).

For the extra large organizations (you can think big banks - Chase, big tech - Netflix, big healthcare - CVS, big retail - Amazon), it’s not uncommon to have many technology stacks. However, it’s more of the “what tool does the job the best” rather than the “Oh, I like this new programming language, let me try it”.

For most organizations, “as few technologies as possible” is the strategy.

What About Database?

This demo uses Redis, which is a key-value database. One could argue that a DevOps Engineer needs to understand SQL databases. I’m not against it, but you don’t usually need it. What you need is to understand how to provision a database and how to set up monitoring around it, and then a development team will configure it however they like it. This might be a hot take, so be it :)