Operations | Monitoring | ITSM | DevOps | Cloud

Many of the multi-faceted applications development teams deploy every day are loosely coupled and every service exists to power another service. Most teams developing fullstack applications know that testing the communication between these services essential. Part of the process is testing HTTP request endpoints, and this tutorial focuses on exactly that. I will lead you through learning how to extend the k6 framework to test our HTTP endpoints.

Together with the community, JFrog pioneered what we now know as DevOps with a focus on binaries (aka software packages, artifacts or images). A decade ago, no one thought binary management would be a thing — now it’s a standard most companies can’t live without. Back then, we said software universality would be necessary, and now others follow suit. People thought cloud would be a single-vendor decision.

Are your cloud costs out of control? Do you struggle with cost overruns or going over your cloud budget? Forecasting costs accurately can help you create a realistic cloud budget you can stick to and prevent cloud bill surprises. In this guide, we’ll cover why it’s so challenging to predict cloud costs and techniques you can use to create an accurate budget your organization will be able to maintain. Table Of Contents.

Hiring a DevOps engineer is a common practice at most IT companies. Having a DevOps developer in your team usually results in making releases more often, faster and better than competitors not implementing a DevOps strategy. Today hiring a DevOps engineer is also relevant for industries other than those from the IT world. Businesses from startups to large enterprises are increasingly thinking: Why not introduce DevOps?

Let’s remember the time in the 2000s when companies introduced their cloud computing offerings at a large scale. New services were put into the popular IaaS, PaaS, and SaaS categories. New kinds of storage and messaging technologies were promoted. Also, novel approaches were discussed, such as designing applications for horizontal scalability and eventual consistency.

Here at LogicMonitor, we’re really big on extensibility and automation. We’re constantly adding to our catalog of monitoring coverage and ensuring that setup is as simple as possible. We also monitor almost any data you can expose on a network. People have done way more with LogicMonitor than we would have ever imagined, and I’m extremely excited to announce our next step in that commitment to extensibility and automation.

Ask any software engineer about the best way to do something and they’ll likely tell you “it depends.” Every project and team works differently and has specific concerns, requirements, and opinions, adding complexity on top of the technical and operational complexity of software development. The challenge lies in managing the work and emergent complexity while staying abreast of industry best practices in a way that fits our teams’ particular processes and environments.

Continuous integration (CI) and continuous delivery or deployment (CD) cover the process of automatically merging, building, and testing code changes ready for release, and – in the case of continuous deployment – releasing those changes to users. If you’re developing software for others to use, you’ll need to go through some form of build and test process before you make your latest changes available.

Over the last several years, systems architects have had to make sure their systems are cloud native, with applications that are optimized for scalable cloud technology infrastructure. In today’s environment, you should be asking whether your solutions are cloud nimble as well. For the modern enterprise, cloud computing is now the default model for applications, storage, and compute.