DevOps in Real Life - what an Experienced Architect Looks for

Поділитися
Вставка
  • Опубліковано 19 вер 2024

КОМЕНТАРІ • 65

  • @GrumpierByTheDay
    @GrumpierByTheDay 2 роки тому +9

    Wow. This is incredible content. Put so many things into context for me. Thank you 1000x for putting this together.

    • @JulieNgTech
      @JulieNgTech  2 роки тому

      Thanks for the feedback Nate. Glad to hear it was helpful. Are there other topics where you think this type of "connecting the dots" videos would be useful?

  • @LisandroBeltramino
    @LisandroBeltramino 3 роки тому +6

    The best content ever on these topics! Keep it up!

    • @JulieNgTech
      @JulieNgTech  3 роки тому

      Thanks Lisandro! I'll continue to make and post more videos :)

  • @henryng5047
    @henryng5047 2 роки тому +4

    This is a great video! I am a new Devops enginee, was confused in my position sometimes due to the wide range of tasks, from VM administration, identity management, and release deployment.... more and more.... After watching your videos, I know the success criteria as a Devops engineer, helping me set up the goals for studies and work quality improvement.

    • @JulieNgTech
      @JulieNgTech  2 роки тому +1

      Thanks Henry! I'm glad that the videos are helping. And really cool that we have the same last name 😄

    • @henryng5047
      @henryng5047 2 роки тому

      @@JulieNgTech Yeah ! We have the same last name :D Long working hours in front of a computer can bring us lot of health issues, it's always suggested doing relaxing exerises e.g. Yoga or even physiotherapy exercises everyday or every few hours , take care.

  • @iamdedlok
    @iamdedlok 3 роки тому +4

    This was an amazing video. I was looking for guidance on DevOps, and this video just clued me into what are the gaps in my knowledge, and what I should be paying more attention to. Thanks, Julie, subbed! I am going to share this with my colleagues, and I will have to go through individual sections of this video again.
    Well done and salute!

    • @JulieNgTech
      @JulieNgTech  3 роки тому

      Awesome Rahul, thanks for the great video. Actually out of all the videos I've made, this one is one of my favorites because it's what I do in real life with Azure customers. I actually want to do more "reviews" and "in real life" videos with cloud engineering. Do you have any specific questions?

    • @bradley5com
      @bradley5com Рік тому

      What skills would you prioritise learning to be a Devops engineer coming from a non technical background

  • @alexacevedo9789
    @alexacevedo9789 Рік тому +1

    Hi Julie , great content .... more please

    • @JulieNgTech
      @JulieNgTech  Рік тому

      Thanks for the feedback :) I have some things on a backlog. Anything in particular you liked?

    • @alexacevedo9789
      @alexacevedo9789 Рік тому

      Hi @@JulieNgTech Thanks for asking, very kind => Terraform IaC & Blue Green Deployments on Azure

  • @SamuelCharlesInnes
    @SamuelCharlesInnes 3 роки тому +1

    Just discovered your work on blog and videos, super helpful. Thanks very much for taking the time to do this.

  • @tomazstih5382
    @tomazstih5382 9 місяців тому

    Julie, you're worth your weight in gold. Thank you for your videos.

  • @Octavian82
    @Octavian82 Рік тому +1

    Hey Julie, great video! Learned a few new things despite doing it for years. Keep it up!

    • @JulieNgTech
      @JulieNgTech  Рік тому +1

      That's a real compliment. You're one of the first people who taught me git. I still remember the first time I had a git error and I think it was either you or Max who came over and said sorry I don't understand the GUI, I need to fix this in the command line - which is totally my line now 😅 hope you're doing well!

  • @ICEFIR3
    @ICEFIR3 3 роки тому +1

    Thanks for sharing your experience and insights! :)

  • @doctordorkmeister5330
    @doctordorkmeister5330 Рік тому

    Git is the home for cyber ethics. A postmodern cathedral of morality

  • @falanges5301
    @falanges5301 Рік тому

    You're amazing Julie! thanks so much for all your sharings!

  • @sixdonuts
    @sixdonuts 2 роки тому

    Thank you for this video and I hope your hand gets better.

  • @MrVanAnderson
    @MrVanAnderson 3 роки тому +1

    Liking the channel and content! Subscribed!

  • @DD-ds7ui
    @DD-ds7ui 11 місяців тому

    best channel. thank you UA-cam algorithm :)

  • @ToksNation
    @ToksNation Рік тому

    This is gold

  • @viniciuspereira95
    @viniciuspereira95 14 днів тому

    I'm really sad that you're not bringing out new videos often.

  • @user779hjg45
    @user779hjg45 Рік тому

    Hi Julie. First of all thank you for this great video. By the way, It looks like the standard-version is deprecated. What are you using now?

  • @TheRandymanhansen
    @TheRandymanhansen 2 роки тому

    I love this video! I'm currently changing my career to DevOps :)

    • @JulieNgTech
      @JulieNgTech  2 роки тому +1

      Glad it was helpful! Good luck with the career change. DevOps is quite fun :)

    • @TheRandymanhansen
      @TheRandymanhansen 2 роки тому

      @@JulieNgTech thank you so much :)

  • @aldodfm
    @aldodfm 3 роки тому +2

    Really enjoy the video!
    I was missing something about Testing on DevOps on Real life, do you have some recommendations? like maybe have testing on CI part and Testing on CD part?
    Make sense to avoid "Forks" on Innner Source approach ?

    • @julieng252
      @julieng252 3 роки тому +2

      Thanks for the feedback Aldo :)
      No, forks are generally good! In the Jenkins Pipeline Library example, looking back, I think one of the biggest mistakes we made was not having a release management and versioning concept to begin with *and* communicating it to teams. We just gave them a library, which they integrated by referencing the git repository - and the default branch was not stable. We should have had a stable branch, or better yet, versioning from the start. Because we broke many peoples' builds, we lost their trust. So they just developed their own forks. We also never really explained how contributing back should work because we didn't have a concept. We were also just learning :) like I said in the video. Looking back, the developers were shipping and that's most important.
      What kind of recommendations were you looking for?
      Unit tests are the most straight-forward and a must. My other hands-on experience was with end to end testing and I want to do an article and video about that. But it's a lot of work because of the infrastructure needed to deploy a bunch of build runners with Selenium.

    • @aldodfm
      @aldodfm 3 роки тому

      @@julieng252 thx for the answers. Really appreciate. I'm always looking for recommendations, experience, etc.
      Right now I'm thinking in a collaborative way of sharing and contributing in Azure resource templates. As you say the best way is communicate properly before doing anything.

    • @JulieNgTech
      @JulieNgTech  3 роки тому +1

      Sharing ARM Templates is much more challenging 😓 because ARM has the concept of "linked" templates that have to be available via a URI, which is why you see lots of blob storage links with SAS tokens 😒
      But I think we've learned from others and you should check out Bicep, which has the concept of modules, which can be referenced as local files. This means you can share them via git as submodules. Far from ideal because submodules point to specific commits, not tags. But it would work until Microsoft releases a way to do proper module sharing via publishing or a registry.
      github.com/Azure/bicep

  • @AungBaw
    @AungBaw Рік тому +1

    Amazing experience, feels like cold shower 🚿

    • @JulieNgTech
      @JulieNgTech  Рік тому +1

      That's one way to describe it 😅 thanks for the feedback!

  • @nomadic_shrek
    @nomadic_shrek 3 роки тому +1

    We need more videos on governance :)

    • @JulieNgTech
      @JulieNgTech  3 роки тому

      Agreed. I'm trying to convince work to let me record one for them. It would be a walkthrough of this doc I wrote docs.microsoft.com/en-us/azure/cloud-adoption-framework/secure/best-practices/secure-devops
      Is that helpful?

  • @lukevandam7610
    @lukevandam7610 Рік тому

    this video........
    This video turns me OWN!!!!!1

  • @ynuxtechblog5373
    @ynuxtechblog5373 2 роки тому

    Just watched this twice, i wished you could have a look at our project. These are exactly the topics that we are struggling with, and exactly the right questions to ask. Are you still open to discussions? Is this a valid environment / release / branching strategy: docker based; dev - int - prod environments, feature branches + main. Build and unit tests on dev. At merge request to main -> push to registry, pull and deploy to integration, do the tests with mock data (or anonymised prod data). At git tag -> pull and deploy to production.

    • @JulieNgTech
      @JulieNgTech  2 роки тому +1

      Hey, it's a great question but not one that's possible to answer in a comment thread. A good answer takes the people, their business scenario and existing experience level into account. Are you an Azure customer and you qualify, you can apply to FastTrack for Azure program, which I am a part of. Engineers like myself do 1:1 reviews with customers. But you have to qualify... if you do, feel free to mention my name. That would support my time and effort on this channel :)

  • @aymanpatel5862
    @aymanpatel5862 3 роки тому +1

    For DB migration, would it be more beneficial to use SQL queries or migration tools such as flyway or liquibase?

    • @JulieNgTech
      @JulieNgTech  3 роки тому +2

      Personally I prefer tools or code because they help me write or even provide the "down" version of the migration as well, in case it fails.
      Other people can probably write the down SQL too. But I can't 🙃

  • @owenzmortgage8273
    @owenzmortgage8273 2 роки тому

    What happened to her left eye when she talking. Great videos thanks for sharing

    • @JulieNgTech
      @JulieNgTech  2 роки тому

      LOL 😂 probably lighting? There wasn't anything wrong with my eye. But glad you liked the video :)

  • @sergei5879
    @sergei5879 3 роки тому

    Hi Julie, I saw you quite open to questions, I have one.
    terraform destroy - we had issues with destroying while it has to destroy KeyVault with secrets in it. So now for a destroy we have to run it in pipe (using azure devops) wait for it fails, delete manually KV from TF state and then rerun destroy. Quite a painful process - but we haven't been able to find a way, considering we need to destroy KV, not just secrets.
    Many thanks in advance for any tips.

    • @JulieNgTech
      @JulieNgTech  3 роки тому

      Hi Sergei, what's your key vault purge settings per registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/key_vault ?

    • @JulieNgTech
      @JulieNgTech  3 роки тому

      I actually was working on a demo of created service principals and saving their credentials in Key Vault. See github.com/julie-ng/terraform-keyvault-demo
      I ran it a few times during meetings and it worked *most* of the time. Sometimes Terraform got stock removing the Key Vault Access Policy. But I am not sure if that is an ARM API issue. I couldn't get it consistently to fail though. Have you double checked your Key Vault purge and delete settings?

  • @engineeringoyster6243
    @engineeringoyster6243 2 роки тому

    ADO has such a confusing and counter-intuitive user interface. The documentation is terrible and is not focused on "worker-bees." Out of all the types of users who use ADO, developers who only write User Stories, participate in Daily Scrums and Demonstrations and Retrospectives for each Sprint. Yet, there is minimal documentation on how to operate the ADO software for these narrow actions. Last week I had 4 User Stories to enter by Friday. I started on Tuesday and spent 10 hours thru Thursday. Yet I still required an additional hour of one-on-one turoring from my lead. And still, on Monday, I still found some errors in the User Stories, requiring rework.
    Every little thing that you do in ADO is complex and cumbersome.
    An effective work around might be to have a template Excel spread sheet with the few required blocks of data and then have a translator /importer that could harvest the User Story data from Excel and import it into ADO.
    One graphic impediment of ADO is that the boundaries and boarders between elements shown on the screen are visually difficult to see. Further, each "sub-window" shown on the screen contains far more data than can be shown. So, the excess data are just hidden, beyond the sub-window borders. So, if the sub-window has 20 words of text, only 3 or so will be displayed. Rendering the information mostly unusable.
    I've occasionally worked with software architects over the past 15 years or so. I've repeatedly asked them to describe their function. They never can provide an answer. I sincerely do not see any value for their participation.
    I could understand if their answer was that they do the preliminary design of the software. But, they have been clear that that is not their job.

    • @JulieNgTech
      @JulieNgTech  2 роки тому

      I'm sorry you feel that way. But I can understand it's frustrating. I personally don't use any of the repo or user story functionality (I prefer GitHub). And because I don't work on the product, I can't comment

    • @engineeringoyster6243
      @engineeringoyster6243 2 роки тому

      @@JulieNgTech Thanks forvreplying. It is astounding to read that you don't have any familiarity with the core functionality of ADO. So where does a sincere, novice user go to find assistance? More importantly, if you don't use ADO like this, why does anyone use ADO? Who are the intended users of ADO? How does ADO bring value?

  • @DallasFort1857
    @DallasFort1857 Рік тому

    should I start as a developer and then make my way towards devops engineering? or can I become a devops engineer without going the full stack developer route?

    • @JulieNgTech
      @JulieNgTech  Рік тому +1

      You can definitely become a DevOps engineer without going the full stack developer route. If you have developer experience, DevOps becomes easier to understand and apply. But you can achieve the same result by working well with developers. In terms of how you should start your career, what do you enjoy? If you don't know, dip your toes in your options until you can decide which one to go deeper in. And be open that you might choose a bad fit on the first try. But know you can always switch.
      When Microsoft recruited me from my old job, they convinced me to specialize in AI and Data Science because they were upcoming industries. Looking bad that was a bad idea for me because I was already invested in AppDev and DevOps and could contribute more by leveraging existing strengths which I enjoy.
      Hope that helps!

  • @RaviSingh-ix3nr
    @RaviSingh-ix3nr 2 роки тому

    Watching this I think 10th time. Taking notes each time and working on those pieces, however, I'm not feeling confident about it. As I told you before, I started DevOps this year only. Learned Git, Docker, Jenkins, Ansible, Kubernetes (CKA Certified), created 1 AWS Code Pipeline. Terraform is next on my list. What kind of project should I do? What programming language is must for DevOps? If you get time, please let me know how can I improve in DevOps? What areas should I focus more? Thanks in advance.

    • @JulieNgTech
      @JulieNgTech  2 роки тому +1

      Hey Ravi, like most things in life, when you want to improve, you have to go out there and put in the hours. Find a project, even if it's just a hobby project and go work on it. Some developers who are learning on the side will over-engineer their personal blogs - easiest learning opportunity for everyone. If you can learn during work hours, that's even better! Try putting al those tools together. You could try for example running your own Jenkins cluster on Kubernetes. And CI/CD the hell out of all of it, e.g. dev vs prod, etc. That's a kind of "putting it altogether" project that may be helpful for you.

    • @RaviSingh-ix3nr
      @RaviSingh-ix3nr 2 роки тому

      @@JulieNgTech Thanks a ton :)

  • @raghavgupta1157
    @raghavgupta1157 3 роки тому

    Idk any of the answers :p.

    • @JulieNgTech
      @JulieNgTech  3 роки тому

      That's also good! It means you have a good opportunity to learn something new and/or refresh what you already know. I ask myself many of these questions al the time and often they change per project - or just me getting older ;-)

  • @mhalton
    @mhalton 2 роки тому

    List problems with no solutions.

    • @JulieNgTech
      @JulieNgTech  2 роки тому

      There is no one size fits all solution if that's what you're looking for. There's different solutions for everyone because we all have different scenarios, requirements and experience levels. This video is about how to approach finding YOUR solution.

  • @ER-zj3jv
    @ER-zj3jv 2 роки тому

    this is free?

    • @JulieNgTech
      @JulieNgTech  2 роки тому +2

      Yes, I am giving away my knowledge and experience completely for free :) I did not study IT and learned it all on my own via the internet. So now it's time for me to give back.

    • @ER-zj3jv
      @ER-zj3jv 2 роки тому

      @@JulieNgTech Thanks Julie. Your content is very helpful.