devopsy.kinsta.cloud

Author: devopsy.kinsta.cloud

  • New Relic Achieves AWS Lambda Ready Designation to Help Developers Function Faster on Serverless

    New Relic Achieves AWS Lambda Ready Designation to Help Developers Function Faster on Serverless

    John Kinmonth from New Relic writes about how New Relic Serverless received AWS Lambda ready designation.

    The rise of serverless architecture has empowered developers to take advantage of increased agility, scalability, and efficiency for customer-facing applications and critical workloads.

    However, as infrastructure is abstracted away from the enterprise, new complexities emerge that make it difficult to debug and monitor applications. New Relic Serverless enables developers to monitor, visualize, troubleshoot, and alert on all of their functions in a single experience so they can function faster.

    And today, New Relic announced it has achieved the AWS Lambda Ready designation, part of the Amazon Web Services (AWS) Service Ready Program. This distinction recognizes that New Relic Serverless has demonstrated successful integration with AWS Lambda.

    Read the full blog post here:

    https://blog.newrelic.com/product-news/new-relic-aws-lambda-ready-designation/

  • Startup for Startup: How actions define company culture

    Startup for Startup: How actions define company culture

    In this episode of Startup for Startup, Roy Mann and Eran Zinman, monday.com’s founders, together with Lior Krengel, break down the six cultural attributes that lie at the core of monday.com’s culture. They discuss how the culture of a company is formed, what impact does the hiring process have on a culture, and why we don’t believe in hanging ‘culture posters’ on the wall.

    00:36 – What is culture to you?
    03:55 – Is the decision to hire ability over team collaboration the right one?
    06:25 – What does culture look like for new people joining the company?
    07:56 – How is culture formed?
    09:15 – Does culture determine the success of a company?
    11:14 – The six different areas we believe in.
    14:35 – What decisions have we made that support us being product-centric?
    16:14 – What does customer centricity really mean to us?
    20:25 – How we define ownership in a sentence.
    27:27 – What does inclusion mean at monday.com?
    36:05 – What does impact look like in a daily setting?
    42:01 – What is speed and why is it different for SaaS?

    Listen to the full podcast here:

     

  • Announcing Dispatch 1.1 – Cloud Native CI/CD for Enterprise-Grade GitOps

    Announcing Dispatch 1.1 – Cloud Native CI/CD for Enterprise-Grade GitOps

    Rahul Dabke from D2iQ writes about the newest release of  Dispatch useful for CI/CD, developer agility, and collaboration.

    D2iQ is proud to announce Dispatch 1.1 — a fast-follower to Dispatch launch where we accelerate CI/CD pipelines and smoothen the user experience for developer onboarding.
    Here are noteworthy highlights of the Dispatch 1.1 release:

    • Accelerate CI/CD pipelines with open source solutions
    • Improved developer-operator collaboration
    • Improved Navigation

    Learn more about the highlights of the Dispatch 1.1 release here:

    https://d2iq.com/blog/announcing-dispatch-1-1-cloud-native-ci-cd-for-enterprise-grade-gitops

     

  • What is Digital Operations Management?

    What is Digital Operations Management?

    Digital Operations Management arms organizations with the insights needed to turn data into opportunity across every operational use case, from DevOps, ITOps, Security, Support, and beyond. This interactive, drawn-out video gives you a great visual perspective and understanding of what digital operations managaement is all about, and why it is so vital to software engineers and their use cases.

    To see more, watch the full video here:

    [su_youtube url=”https://www.youtube.com/watch?v=d0uZF2r0er8&feature=youtu.be”]

     

  • Identifying and resolving security code vulnerabilities using Snyk in AWS CI/CD Pipeline

    Identifying and resolving security code vulnerabilities using Snyk in AWS CI/CD Pipeline

    The majority of companies have embraced open-source software (OSS) at an accelerated rate even when building proprietary applications. Some of the obvious benefits for this shift include transparency, cost, flexibility, and a faster time to market. Snyk’s unique combination of developer-first tooling and best in class security depth enables businesses to easily build security into their continuous development process.

    Even for teams building proprietary code, use of open-source packages and libraries is a necessity. In reality, a developer’s own code is often a small core within the app, and the rest is open-source software. While relying on third-party elements has obvious benefits, it also presents numerous complexities. Inadvertently introducing vulnerabilities into your codebase through repositories that are maintained in a distributed fashion and with widely varying levels of security expertise can be common, and opens up applications to effective attacks downstream.

    To read more, click on the link below:

    https://aws.amazon.com/blogs/devops/identifying-and-resolving-vulnerabilities-in-your-code/

     

  • Hybrid and Multi-Cloud Is Tired. Federated Distribution Is Wired

    Hybrid and Multi-Cloud Is Tired. Federated Distribution Is Wired

    Chris Gaun and Max Werner from D2iQ write about expanding upon Kubernetes by using new distribution and Day-2-ifying practices.

    Not much has changed about end users’ hybrid and multi-cloud strategy in 10 years. Now that Kubernetes is everywhere—GKE, EKS, OKE, AKS, DIY, Konvoy—it is time to expand upon the staid approach by deploying a distribution on top of and Day-2-ify-ing those existing Kubernetes clusters.

    The Kommander product strategy has always assumed that users will sometimes have existing Kubernetes clusters or have already decided on a particular vendor/provider. Kommander still delivers value to those customers. One way we planned to do that before even the first line of code was committed on any of our products was to take the Day 2 Kubernetes-based addons from Konvoy and federate them out to 3rd party clusters, making those clusters Konvoy-like and giving users the same operational view in Kommander no matter which managed cluster lies beneath. Over time, D2iQ will continue to expand our roster of  Day 2 addons and give operators more consistent capabilities on all their clusters.

    Read the full blog post here:

    https://d2iq.com/blog/hybrid-and-multi-cloud-is-tired-federated-distribution-is-wired

  • Three Mistakes to Avoid When Migrating to the Cloud

    Three Mistakes to Avoid When Migrating to the Cloud

    Migration and modernization is a process – it doesn’t all happen at once, and some applications don’t make the journey. AWS and CloudBees help customers navigate cloud adoption and DevOps transformation with tools and practices that help customers make good decisions on how to move, migrate, rebuild or replace the components you need.

    Many enterprise software companies on the road to DevOps transformation are tasked with migrating legacy applications to the cloud. But deconstructing the monolith and refactoring applications isn’t always easy. This is especially true for highly regulated industries such as government, healthcare and financial services where change management is rigorous. The DevOps challenges preventing success often lie in the ways these teams work. CloudBees and AWS can help you avoid the pitfalls and give you the best practices and tools required for lasting DevOps transformation.

    Check out this webinar recording, where we explore the top three mistakes enterprise software companies make on their journey to the cloud. We’ll also tell you what they should have done instead.

    1. Can’t let go of ‘Big Bang or Bust’ deployments. Embrace smaller teams and iterative development which will yield smaller, more frequent releases. Then choose a CI tool that supports your mission.

    2. Force fitting old processes into new tools. Take advantage of the modern best practices built into the toolset to guide success.

    3. Believing automation is the end goal. The actual endpoint is faster, higher quality delivery of software. Automation is a means to that end, and choosing a CI solution that can automate a wide, varied ecosystem is critical (especially when dealing with the modernization of legacy applications.)

    As the leader in DevOps, CloudBees CI, built on Amazon EKS, has undergone rigorous security hardening, making it a safe choice for even the most regulated environments, such as the DoD. Amazon has recently added support for EKS to the AWS GovCloud Marketplace and CloudBees CI is now live. If you’re looking to up your security game, this webinar will equip you with the knowledge you need to take DevOps to the next level in the cloud.

    To learn more about how to avoid these mistakes when migrating to the Cloud, click the video link below:

    https://www.youtube.com/watch?v=u8CLHGy7Eh4&feature=youtu.be&mkt_tok=eyJpIjoiTkdVellUTXpOamd4T1RFeSIsInQiOiJjaWUzMWhsb3k1YWtPaUlpZnlLbXJwNmIrXC9FMFBrY0R5MnRGbWRuV1RzV0h4cTczVFNCOWR2MEViUE9nY1Bua0paTnhHUkxZRG54RFlMVjdMeWZXY3c9PSJ9

     

  • Instrumenting distributed systems for operational visibility

    Instrumenting distributed systems for operational visibility

    David Yanacek, a Senior Principal Engineer working on AWS Lambda, writes about using distributed systems for more operational visibility.

    When I joined Amazon after college, one of my first onboarding exercises was to get the amazon.com web server up and running on my developer desktop. I didn’t get it right on the first try, and I wasn’t sure what I did wrong. A helpful coworker suggested that I look at the logs to see what was wrong. To do so, he said that I should “cat the log file.” I was convinced they were playing some sort of prank on me or making a joke about cats that I didn’t understand. I only used Linux in college to compile, use source control, and use a text editor. So I didn’t know that “cat” is actually a command to print out a file to the terminal that I could feed into another program to look for patterns.

    My coworkers pointed me to tools like cat, grep, sed, and awk. Equipped with this new toolset, I dove into the amazon.com web server logs on my developer desktop. The web server application was already instrumented to emit all kinds of useful information into its logs. This allowed me to see what configuration I was missing that prevented the web server from starting up, that showed where it might have been crashing, or that indicated where it was failing to talk to a downstream service. The website is made up of a lot of moving pieces, and it was essentially a black box to me at the beginning. However, after diving headfirst into the system, I learned how to figure out how the server worked and how to interact with its dependencies just by looking at the output of the instrumentation.

    Download the full white paper here:

    [su_button url=”http://devops.staging.wpengine.com/wp-content/uploads/2020/07/instrumenting-distributed-systems-for-operational-visibility.pdf” target=”blank” background=”#ef2d3f”]Download Now[/su_button]

  • Going faster with continuous delivery

    Going faster with continuous delivery

    Mark Mansour, a senior manager of software development at Amazon Web Services, writes about continuous delivery at AWS.

    Over 10 years ago, we undertook a project at Amazon to understand how quickly our teams were turning ideas into high-quality production systems. This led us to measure our software throughput so that we could improve the speed of our execution. We discovered that it was taking, on average, 16 days from code check-in to production. At Amazon, teams started with an idea, and then typically took a day and a half to write code to bring the idea to life. We spent less than an hour to build and deploy the new code. The remainder of the time, almost 14 days, we spent waiting for team members to start a build, to perform deployments, and run tests. At the end of the project, we recommended automating our post check-in processes to improve our speed of execution. The goal was to eliminate delays while maintaining or even improving quality.

    Amazon had already built software development tools to make our software engineers more productive. We created our own centralized and hosted build system, Brazil, that executes a series of commands on a server with the goal of generating an artifact that could be deployed. At this point Brazil didn’t listen to source code changes. A person had to initiate a build. We also had our own deployment system, Apollo, which required a build artifact to be uploaded to it as part of initiating a deployment. Inspired by the interest in continuous delivery occurring in the industry, we built our own system, Pipelines, to automate the software delivery process between Brazil and Apollo.

    Read the full white paper here:

    [su_button url=”http://devops.staging.wpengine.com/wp-content/uploads/2020/07/going-faster-with-continuous-delivery.pdf” target=”blank” background=”#ef2d3f”]Download Now[/su_button]

  • Solution Brief: Starter Pack For GitOps & Kubernetes – The Shortcut to Day 2 Success

    Solution Brief: Starter Pack For GitOps & Kubernetes – The Shortcut to Day 2 Success

    GitOps is the state of the art for cloud native software development. Assembling the necessary tools and technologies, while obtaining the proper training, can raise the bar high enough to prevent projects from reaching success. The starter pack for GitOps and Kubernetes is designed to provide everything needed to lower the bar and accelerate GitOps projects.

    Click here to download the starter pack:

    [su_button url=”http://devops.staging.wpengine.com/wp-content/uploads/2020/07/SB-GitOps-and-K8-Starter-Pack-v2.pdf” target=”blank” background=”#ef2d3f”]Download Now[/su_button]