Answers: <p>Your question is quite vague/generic.</p>
  
  <p>People store their source code (or generally, files) in git; let Jenkins run jobs (like CI/CD pipelines), use Docker to put their software into well-defined containers, Nagios to monitor their systems, ELK to collect, store and visualize (mostly logging, event) data, AWS to host their stuff, and Chef to manage their configurations.</p>
  
  <p>If you are studying that and learning about it, then you should have gotten that kind of information, really. The scenario in real world companies is simply to use those tools for what they are made, in different combinations as needed.</p>
  
  <p>If you really have just gotten some deficient information from your college or wherever you studied those things, then get a book like The DevOps Handbook and give it a read. It should clear up how all of this would work together in the real world.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-10-15T19:44:53.523Z
Answers: Sorry to say, but none of this is true if the question would be related to "mainframes" ... running an OS like "zOS" (with the "z" for "zero downtime"). Want to update your answer?
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-10-15T19:56:09.317Z
Answers: @Pierre.Vriens, I cannot relate your comment to the question or my answer at all. Did you intend to post it somewhere else?
Answers: AnoE
Answers: CC BY-SA 3.0
Answers: 2017-10-15T20:24:59.957Z
Answers: DevOps also applies to mainframe ... while the question seems to be OS independent ... Though OPer might not even realize that there are still companies depending on them, such as banks, airlines, etc. Ever wondered why online banking never appears to be down? Or what it costs for such systems to be unavailable for, say, 1 second?
Answers: Pierre.Vriens
Answers: CC BY-SA 3.0
Answers: 2017-10-16T02:42:01.310Z
Answers: Seems like a solid answer to me. The vague question named some tools and sort of asked when they would be used. The question did ask for a "scenario," but still a decent answer, IMHO.
Answers: Stephen C
Answers: CC BY-SA 3.0
Answers: 2017-10-15T18:43:24.607Z
Answers: 2017-10-15T18:43:24.607Z
Answers: AnoE
Body: <p>i am a devops learner, just finished graduation actively looking for jobs in the field of DevOps.</p>
  
  <p>I am learning many tools like GIT, Jenkins, Chef, Docker , Nagious, ELK, AWS, etc.</p>
  
  <p>Can anyone link all the DevOps tools together and give me a scenario where and how a company uses these tools at different times?</p>
  
Tags: <docker><jenkins><amazon-web-services><chef><kubernetes>
Title: Creativity use case scenario?
UserDisplayName: EDU_EVER
ThreadText: # Creativity use case scenario?
  
  (Asked by: username_0 on 2017-10-15)
  
  i am a devops learner, just finished graduation actively looking for jobs in the field of DevOps.
  
  I am learning many tools like GIT, Jenkins, Chef, Docker , Nagious, ELK, AWS, etc.
  
  Can anyone link all the DevOps tools together and give me a scenario where and how a company uses these tools at different times?
  
  **Tags:** docker, jenkins, amazon-web-services, chef, kubernetes
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-10-15. Score: 3
  
  Your question is quite vague/generic.
  
  People store their source code (or generally, files) in git; let Jenkins run jobs (like CI/CD pipelines), use Docker to put their software into well-defined containers, Nagios to monitor their systems, ELK to collect, store and visualize (mostly logging, event) data, AWS to host their stuff, and Chef to manage their configurations.
  
  If you are studying that and learning about it, then you should have gotten that kind of information, really. The scenario in real world companies is simply to use those tools for what they are made, in different combinations as needed.
  
  If you really have just gotten some deficient information from your college or wherever you studied those things, then get a book like The DevOps Handbook and give it a read. It should clear up how all of this would work together in the real world.
  
  > **Comments:**
  > **username_2**: Sorry to say, but none of this is true if the question would be related to "mainframes" ... running an OS like "zOS" (with the "z" for "zero downtime"). Want to update your answer?  
  > **username_1**: @username_2, I cannot relate your comment to the question or my answer at all. Did you intend to post it somewhere else?  
  > **username_2**: DevOps also applies to mainframe ... while the question seems to be OS independent ... Though OPer might not even realize that there are still companies depending on them, such as banks, airlines, etc. Ever wondered why online banking never appears to be down? Or what it costs for such systems to be unavailable for, say, 1 second?  
  > **username_3**: Seems like a solid answer to me. The vague question named some tools and sort of asked when they would be used. The question did ask for a "scenario," but still a decent answer, IMHO.  
  
  ---
  
  