The CIO of Africa's largest privately owned Investment Management company — which does $1.6B in revenue — is scaling its use of Germain. In 4-years time, and in parallel to using Germain, this Investment Firm tried a number of Germain, RUM, Observability platform. Most recently they tried NewRelic and Dynatrace, although they've tried others before. They are now expanding with Germain, and we look forward to continuing this journey.

How this Investment firm manages its infrastructure and releases, and how Germain integrates:

Whenever this firm's DevOps Team wishes to release new changes to an API, they build a new docker image. This image is based off a Linux distribution and includes the .NET Core runtime. The Linux distribution they are currently using is Alpine (Ubuntu was used previously). Their DevOps Team then adds its published application code to the image, pushes that image to a container registry, and subsequently deploys that image as a container into a Kubernetes cluster. The DevOps team runs its containers with AWS Fargate (ECS – i.e. without a Kubernetes cluster. Until recently an on-prem Kubernetes cluster was used). AWS manages all of the infrastructure for the DevOps Team, so running a monitoring agent isn't an option for them. Instead, the Germain Team provides a package that is automatically installed as part of its container creation, and Germain features automatically follow.

On the other hand, this firm's Retail team works slightly differently in that its APIs are built with Scala or Go, and it runs Linux containers in Kubernetes. They then use Kubernetes in AWS by making use of AWS’s EKS service, however the Germain package is still provided to them as an automatic installation.

Monitored Technologies:

  • Alpine and Ubuntu-based Kubernetes

  • Appian

  • AWS Fargates

  • GoLang

  • Linux

  • Microsoft Dynamics CRM (Retail, Institutional)

  • .Net CORE (for integration)

  • SAP Success factors

  • Scala