What exactly is DevOps and what’s the learning roadmap.
In: 25
traditional companies were all the same. you had a systems team. they managed the servers. they upgraded them, purchased them, fixed them, etc. you had a database team. they ran the database servers. they did all things related to databases. you had an identity team. they manage the directory that stores all of the users. you had a team that handles security. a team that handles network related things. you had a desktop team. (they handled the computers the employees use). you had a voice team that handles phones. you had computer operators. they sit in the datacenter and run jobs at certain times, and call appropriate people if cooling for the database broke or something. many more specific teams can exist too
in that setup, you had to request things from everyone. if you want to create an app, you need a server for it to run on. so you put in a request to systems team to create a server for you to use. that ticket sits and waits for manager approval. sometimes they schedule a meeting and want to ask you more questions, both for approval reasons, and also so they know all of the details of what you need. then they open a ticket to storage team and ask for more storage because they’re running low. that ticket also needs manager approval. you open a ticket to database team because your app needs to store data. they ask you what users you need. you give them a list. they open a ticket with identity team to create a group for this app, and another ticket to security team to approve of the users an permissions that were requested. if their database storage is low, they might also need a ticket to get that increased too. then your server is ready and you log in, but you realize it doesn’t have access to the database that database team created. so you have to put in a security request to the security team. they schedule a meeting to meet with you to ask why you need this. once that’s done, they approve the request for network team. network team then creates firewall rules to open access between your database and your server. when you consider that some of those teams are swamped, and it has several layers of manager approvals and meetings for discussion, you can see why old app development can take a long time
in devops, the developers (people writing the code, or programmers) can do most of the things they need themselves. the “dev” part of devops is developers. the “ops” part is operations. basically the people on those traditional teams. you’ll still have people that manage some things, but they’re there more for help and to set the rules and such. usually for devops you use tools that make this stuff available for self service. like using a cloud service for example. if you want a server, you log into AWS for example, goto EC2 service page, click a few buttons, type a few things, and minutes later, your server is alive. same with database. you can get everything you need in minutes. things that could have taken several weeks, traditionally. that’s a very simplified example, but i think it should be make it clear what devops is compared to what we used to do traditionally
Latest Answers