In this blog post, we’re answering audience questions related to DevOps, team, and culture from our ‘Building Mobile Apps At Scale’ webinar with Gergely Orosz, Pooja Bhaumik, and Franz Busch.
We love abstractions. We want to make things easier for developers, teams and end users. In doing that, sometimes we build things a little bit too complex for those who don’t already understand the pain points for which the abstraction layers were built. Kubernetes is an example of this; it solves a very real, very painful problem, but it is notoriously difficult to wrap your head around.
For the first time, Kubernetes engineering teams interested in learning more about Speedscale will be able to play with the framework without registering, at play.speedscale.com. Engineers can see firsthand how you: While users won’t be able to actively watch replays run, there are a variety of pre-created traffic snapshots, reports and configs to browse. Engineers will be able to experience the ease with which snapshots are generated for fast, scalable test automation.
Embracing DevOps is not easy. There are a lot of misconceptions about what DevOps is. DevOps is not a team, or a methodology, or a job role. DevOps is a culture founded on a set of work patterns and practices that have an impact on the whole value chain, from business to operations. DevOps helps you move from only having visibility about your own work, to having a birds-eye view and overall understanding of the whole value stream (from business to customer feedback).
If you still rely on big-bang deployments or are ever afraid to break your production environment when you push changes, then it is seriously time to invest in building a strong CI/CD pipeline. Pushing changes quickly and often is critical. The best way to mitigate the risks of new releases is to have a strong deployment strategy in place. Continuous deployment automates the deployment process, which lets you deliver new features and improvements to your applications faster than before.
When the internet first came into existence in 1983, its communication channels didn't exist, and it was just operational enough to be used for research purposes. In 1989, Tim Berners-Lee had the idea to develop a system for the internet using TCP/IP protocols. That public project at CERN introduced HTTP, HTML, World Wide Web (WWW), and a client-server as communication mechanisms. In this post, you'll learn how HTTP protocol works and how new versions brought it to where we are now, with the widely used HTTP/2 in 2021.
Slowly but surely, HTTP/2 is becoming the favored protocol for transporting data files between clients and servers. While HTTP/1 used to be the only way of loading web applications, it’s now lagging behind, especially on the UX front. Since 2015, HTTP/2 APIs have taken the lead with lightning-fast server responses. In particular, they’re responsible for state changes and server responses without the need for browser reloads.
At its most basic level, DevOps—a combination of development and operations—refers to a set of practices that streamline application development at every stage, from building and testing to deploying and monitoring. DevOps largely aims to break down silos and improve collaboration for teams looking to increase agility without compromising on software quality. Unfortunately, traditional high-code methods of development present a few challenges to successful DevOps transformations.
