Operations | Monitoring | ITSM | DevOps | Cloud

Why do some organizations excel in streamlining their database operations and applications development while others find it immensely challenging? Why can some database teams embrace agility while others take months of cycles to deploy even a single line of code? What secret sauce can allow some database teams to work smarter (not harder), streamline database development lifecycles better, get to deployment faster, and create an overall stronger alignment across departments?

As a former incident responder and now as a responder advocate for FireHydrant, I’ve seen the “build vs. buy” debate play out many times. In fact, I even supported the tool that former employers used for managing incidents for years before they decided to buy (more on that in a future blog post).

DevOps is the modern convergence of people, processes and tools to create a continuous software delivery stream. Much like the code it produces, the concept of DevOps itself is continuously adapting to encompass new ideas, methods, and technologies. So what can we expect from the DevOps cultural shift in the future? The delivery stream of yesterday was a segmented process, often separating key teams and concepts into silos where people focused on their individual tasks.

After a long summer break, the Qovery Demo day is back. 🌞 Our last Qovery Demo Day was live on Thursday, the 3rd of November. This event aims to give you insights into what we did during the past month and what’s next and showcase some of our new features. During this demo day, Romaric (CEO at Qovery) and Alessandro (Lead Product Manager at Qovery) joined me to talk about RBAC, Containers and Deploying Jobs and here is the recap.

At the start of October, Dinesh Majrekar, CTO, and Mark Boost, CEO at Civo spoke at KubeCrash, about application deployments of old, cloud-native processes of today and edge native deployments of the future. Watch their session below to learn about the challenges we are about to face with an edge-first architecture and what we can do today to be ready. We then took to Detroit for KubeCon + CNC NA 2022 where we hosted an array of talks, workshops, and events.

In networking, latency - sometimes referred to as 'lag' - is the delay between a client request and the service provider's response. In a cloud environment this could be a developer or end-user client request, and the cloud service provider’s response. Or for multi-cloud, it could be one application in a cloud instance, talking to another application in another cloud instance. But no matter which type, latency can have a real impact on an organisation.

Just as there are a handful of stages to describe the financial journey from startup to established company — pre-seed and seed funding, followed by series A, B, and C funding — there are also stages to the process of achieving a healthy understanding of your costs.

Both servers and software development use Linux. Today, Linux distributions are used by the vast majority of electronics and embedded systems. Worldwide, Linux servers make up about 90% of all internet servers. Additionally, the Linux kernel is used by around 80% of all smartphones. Today, every system in the world is linked via a network. Information exchange across systems requires network connectivity. Computer networking refers to communication over the internet as well as within a network.

Modern applications are a web of interdependent services. As applications grow in size and complexity, and as more engineering teams adopt service-based architectures like microservices, this web becomes deeper and denser. Eventually, keeping track of the interdependencies between services becomes a complex and time-consuming task in and of itself. In addition, if any of these dependencies fails, it can have cascading impacts on the rest of your services and on the application as a whole.