2 min read

Task Objectives

  1. How would you setup your Infrastructure?
  2. How would you setup your infrastructure monitoring?
  3. How would you setup your log monitoring?
  4. How would you setup up your CI/CD workflow?
  5. How would you handle scaling?
  6. How would you handle the setup for new clients?

"DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The contraction of β€œDev” and β€œOps” refers to replacing siloed Development and Operations to create multidisciplinary teams that now work together with shared and efficient practices and tools. Essential DevOps practices include agile planning, continuous integration, continuous delivery, and monitoring of applications."

  • Setup Infrastructure

Our IT infrastructure has designed to use multiple platforms and toolkits in the current corporation. Our organization wants to have at least 5 DevOps engineers in order to build a high level system that we need to build our projects in the current workflow. As a manager, I have decided with my team to use improved system performance, speed, change management within various platforms, scalable infrastructure and overall customer satisfaction.

There are many tools on GitHub and other code source controls systems based on Git that we can use in order to improve our high level infrastructure as a service. Chef or Ansible can be a great playbook role in this game (our plan), Terraform or AWS CloudFormation and so on. We need to think about this, because if the opportunity is given to us, we need to decide asap to build our system carefully and successfully.

  • Setup infrastructure monitoring

Our IT infrastructure has already decided to use the best tool on the network that is popular, but is very expensive on the marketplace for the companies. Dynatrace plays a really good game on this part. Dynatrace will be setup on the current IT infrastructure of this company to monitor everything about services, servers, and the Linux (or possible Windows) system for memory and other hardware parts.

  • Setup log monitoring

We can also setup log monitoring from the team of developers that wants to have a really good understanding of what is happening on the world of logs with a global search in ELK stack. Kibana works like this. Elastic stack gives us in a local environment to our infrastructure to install it for free and is the source code and data are available on GitHub.

  • Setup CI/CD workflow

Our IT infrastructure has already decided to use Jenkins (older) or GitHub Actions (newer) as supported workflow for CI/CD. We need to cover everything about the requirements of DEV, SIT, UAT and PROD systems in the current workflow. There are freestyle jobs and pipelines that we need to write down carefully to run the current product/project in the given workflow for devs.

  • Handle scaling with Kubernetes

Our IT infrastructure wants to use Kubernetes, but from Microsoft that is called Microsoft Kubernetes Service (MKS) to run and scale in the high level of response to the clients, our micro-services for this sportbook platform.

  • Handle the setup for new clients

This is our end of this story, but new clients needs to know about the characteristics and data that will be used in this current platform. The setup for new clients in the system can be also used via infrastructure code as as service with a good database caching data schema such as Redis and Microsoft technologies based on SQL (Microsoft SQL Server). It is a like a strategy.

Orestis Pantazos

Orestis Pantazos

DevOps Engineer