No-code, low-code, and bring-your-own-code (BYOC) platforms refer to different types of software development approaches that cater to varying levels of technical expertise, allowing users to create applications, websites, and automate tasks with differing degrees of coding requirements.
Anna Kapuścińska is a Software Engineer at Isovalent, who has a rich experience wearing both developer and SRE hats across the industry. Now she works on Isovalent observability products such as Hubble, Tetragon, and Timescape, as well as the respective Grafana integrations for all of them.
When it comes to the relative merits of hybrid work approaches, there can be a range of opinions; some are strong advocates, some see significant downsides, and many fall somewhere in between. About the one thing pretty much everyone can agree upon is that the rise in hybrid work has made the jobs of IT operations teams much more challenging. On any given day, a user may be working in the office, from their home kitchen, a neighborhood café, or just about anywhere else.
TLS certificates are crucial for the secure flow of web traffic, but managing these digital certificates can pose a challenge. Using an ACME-based certificate authority like Let’s Encrypt can automate and simplify the management of issuing these certificates. Certificate management in HAProxy has steadily improved over the years, allowing it to become more flexible and load certificates without restarting.
No matter how much prevention you have, serious security incidents will inevitably occur. Read the next article in our security series that covers how to understand cyberattacks as quickly as possible so that your organization can respond swiftly.
The common failure scenarios that occur in the cybersecurity world are typically assumed to be costs of doing business, but they’re actually more predictable and avoidable than you might imagine. Even if you’ve been lucky enough to avoid failed data sources or backups, a SIEM getting knocked offline, and other cybersecurity attack situations until now — in today’s day and age, they’re still inevitable.
A few months ago, we released Status Pages. This project was quite different from anything we’ve approached before, given that: And our goals were a departure from one's we had set in the past: With this in mind, we worked closely with our designer throughout the process of building Status Pages. Here is how we approached it and a few lessons we learned along the way!
Catalog is really, really powerful. To prove it, our latest product went up against the almighty Thanos and won decisively. Don’t believe us? Just look at how unscathed Catalog was once the dust settled: All jokes aside, we spent months building out what, we think, is one of the most capable products on the market today. Designed to be a map of everything that exists in your organization Catalog can meaningfully help you level up your incident response.
A thin client is a simplified device that relies on a separate server (usually located remotely or in the cloud) to run programs and complete user tasks. It connects to the server through a remote network connection with very little computing happening on an individual user’s device. Because most of the computation occurs and data is stored on the server, thin clients are regarded as a secure efficient option.
