Automation

So, you’re looking to create a new project. But before you start, you must decide which scaffolding generator you’ll use. You have two main tools at your disposal which we are going to compare: Cookiecutter vs Yeoman.

When you’re designing a microservice architecture, there are a lot of questions you have to answer. Some of them make themselves apparent very early in the process.

Today, Kubernetes is the de facto standard for container orchestration, running in approximately half of all containerized environments. Platform and infrastructure teams of all shapes and sizes are accustomed to operating Kubernetes in order to run their organizations’ microservices (and applications) at any scale.

We all know that naming things is one of the two hardest problems in computer science (along with cache invalidation and off-by-one errors.) Naming your microservices is extra hard, as they’re almost like children: they’re practically these living, breathing things that you birth into the world and do your best to make sure they’re set up for success in life (i.e. in production.) Ok, perhaps people don’t agonize over the names of their microservices as much as the names of their children, but it’s still a big enough decision.

A microservice catalog is only as good as the data it contains. OpsLevel is making it easier than ever to keep your service list up-to-date with its new Service Suggestions feature. With Service Suggestions, we automatically discover new services when they get deployed and help you add them to OpsLevel. For services that are already in OpsLevel, we can also help you easily attach those deployment streams to the right service.

A modern software catalog must be automatically kept up-to-date to reduce the burden on developers and build trust. The OpsLevel Catalog Engine is an always-on way to create and maintain an accurate catalog rich with metadata. Read on to learn more.