Operations | Monitoring | ITSM | DevOps | Cloud

Amazon Web Services (AWS) provides three types of Elastic Compute Cloud (EC2) instances; On-Demand Instances, Reserved Instances (RIs), and Spot Instances. EC2 On-Demand instances are the default and most expensive instances. RIs and Spot instances offer discounts of up to 72% and 90% on On-Demand instances, respectively. The Reserved Instances are long-term commitments that guarantee you compute power for a year or three. Spot instances fluctuate in price and availability constantly.

Today I will talk about naming convention because I think this is so critical to implement from day one, and people tend to forget. We earlier addressed the importance of providing a good naming convention to your Logic App name and actions inside your business process. Today we will speak about the Connectors (or API Connections) naming convention.

Even though NoSQL databases like Amazon’s own DynamoDB are very popular today, for many business use cases, there’s almost no way around using a traditional relational database. Amazon Relational Database Service (RDS), released back in October 2009, is one of Amazon’s first cloud services and can therefore be seen as a very mature service.

The term ‘big data’ is used so commonly in research and marketing terms, you would think it’s been here forever. But actually, big data evolved from database marketing (read first efforts of targeted direct mail) in the mid to late 1980’s. This was the first attempt of marketing agencies and large corporations to begin segmenting their customer databases to create different offers based on the demographics or psychographics of their customers.

Aiven gives a secure, fully managed platform for your Apache Kafka®. Want to be 10x more productive into the bargain? Check out Conduktor.

It might appear like a challenging task to move from a centralized point of access to the network and apply a zero-trust security model. But, with growing instances of data breaches, cybersecurity threats, and the need for remote working, zero-trust network access has become a need of the hour for many organizations. It provides a holistic and strategic approach to secure your network and provide adequate access to the required systems.

In this fourth session in our DevOps 101 series, we’re going to delve into Database DevOps specifically. But before we get going, I just want to do a quick check to make sure we’re all on the same page. Donovan Brown’s definition of DevOps seems to have been adopted by almost everyone nowadays because it’s very clear: “DevOps is the union of people, process, and products to enable continuous delivery of value to our end users”.

At Catchpoint, my role can be summarized at a high level as two halves: designing and taking care of Engineering teams – and working with those teams to design and take care of the various distributed systems that run our platform. I recently attended Sapphire Ventures' Hypergrowth Engineering Summit (thank you David Carter and Sapphire for the invitation!) where the sessions focused on creating and scaling high functioning engineering.

In this guide, we’ll set up an OpenTelemetry Collector that collects logs and sends them to Grafana Loki running in Grafana Cloud. We will consider two examples for sending logs to Loki via OpenTelemetry Collector. The first one shows how to collect container logs with a Fluent Forward receiver. The second one shows how to collect system logs with a Filelog receiver.