Nowadays the need to increase our ability to automate and to quickly deploy infrastructure and services has increased tremendously.
So before driving straight into Terraform, let's just focus a bit for a moment on the larger ecosystem that includes Terraform which is DevOps.
The main idea behind DevOps as a I don't know. I call it a movement. You might disagree. I called movement.
It's and this movement's main idea behind this movement is to bring together, two traditionally separate types of teams: have to developers that write the applications and have the operations people know the this is admins the ones responsible for making sure that the code runs properly on any environment starting from the developers laptop or the code is tested for the first time going to the data center of the client or the staging area going to the public cloud and even sometimes in between, and especially with the introduction of numerous public cloud. So have a lot of public clouds.
Nowadays the need to increase our ability to automate and to quickly deploy infrastructure and services has also increased tremendously. Nowadays, when you press that, you know by or deploy a button in a public Cloud expect that thing to be ready right away, in a matter of minutes.
Now traditionally developers needed to focus on just building the application. Testing. It's not worrying about the infrastructure that the code is going to run on not knowing anything about the customer's environment perhaps.
While the operations people only took care of the physical or virtual infrastructure with, you know, everything in it: light computers, storage, networking, securing access, users and so on. So if we were to give us a synonym, let's say to DevOps I would say that this is collaboration. I would call it collaboration between developers and operations.
And this is more I would say more natural kind of collaboration doesn't just imply communication , because he probably had that already. But it's actually about deleting or at least blurring the lines a bit between these two traditional job roles and also reaching out into the others area of expertise.
So developers need to understand how a cloud infrastructure works so that they can package their apps in a more compatible way. The operations team needs to understand that they are not simply providing the infrastructure, but they are also tasked with running real code real applications that they should be aware of.
So this is the major, the major point in the changes that are brought upon by this DevOps movement.
Now what started as a simple idea of collaboration that I just mentioned between developers and operations has grown into a huge ecosystem. And a very interesting and also interactive overview of this can be found on this link on the screen. It's part of digital AI previously part of zbl ABS.
Well, this way of presenting a set of products like a periodic table of elements, of course, is just a Let's call it a marketing stunt that has nothing to do with DevOps, of course, but it does make for a nice presentation and also points out just how huge this ecosystem has become lately.
I could bet that none of you knows or at least has heard of more than half of these tools out there.
So I would strongly encourage you to have a look and decide for yourselves, where a knowledge deep dive makes sense for you in this huge world of DevOps.
Play with this link for a bit to figure it out which of these make sense for you and your future career.
Now to read It either use the link on the screen or just Google search for I know Periodic Table of DevOps or just wait for the PDF presentation to arrive in your inbox after the webinar. But give it a try right.
You probably don't expect them off to be this, I would say developed right pun intended.
So to help navigate this DevOps ocean, we at Bittnet and especially the people in charge of the DevOps, our design project have defined several to learning paths, to guide you in the learning journey, these learning past looks something like this, and there are aligned with specific job responsibilities and include what we consider to be the most relevant tools in each specific field.
Taking you from an associate level to an expert level or from Zero to Hero, we cover pretty much the entire DevOps Loop. Starting from writing and manage the application code moving on to building and release automation with: Jenkins, Configuration Management with tools like Ansible, Chef, Puppet, Deploying and shipping or apps using Docker containers, also going one step further beyond just Containers and doing some orchestration with Kubernetes, Monitoring with Elastic Stack, which you might know know as the elk stack right made up of Elasticsearch, Logstash and Kibana, Prometheus from time series database is great for monitoring and of course security DevOps tools.
By the way, this slide is just the current state of affairs. We are constantly adding more technologies to our offerings. We're not removing anything unlike Netflix or Game Pass.
So we're just adding regarding more and more just to cover as much as we can out of this huge DevOps red.