Designing a production service environment around Apache Kafka that delivers low latency and zero-data loss at scale is non-trivial. Indeed, it’s the holy grail of messaging systems. In this blog post, I’ll outline some of the fundamental service design considerations that you’ll need to take into account in order to get your service architecture to measure up. Let’s start with the basics.
Docker is a PaaS product, developed by Docker.Inc to containerize applications. It does so by combining app source code with OS libraries and dependencies required to run that code in any environment. Kubernetes is a similar tool developed by Google, which scales up this containerized application after deployment. While one works in building the containers the other essentially helps in scaling it up, then why so much buzz around these two?
Most engineering teams are no strangers to key performance indicators (KPIs), those metrics tracking progress toward critical goals and targets. Ideally, tech leaders design KPIs to focus teams on what matters and prove their contribution to the company’s overall performance. Of course, KPI data should also uncover critical information that guides informed decision-making. For engineering teams tasked with managing the customer experience, KPIs often track availability.
Before I dive into the launch of Cycle’s latest feature (and it’s a big one!) I want to share some context about how we got here. Let’s rewind back to 2015: containers, at least in their modern form, had just begun to take the developer ecosystem by storm. At the same time, we at Cycle were watching everything unfold: from Docker’s meteoric rise to the first few releases of tools like Kubernetes, Rancher, and so on.
We spoke with two members from the SRE team, Alex Blyth and Zulhilmi Zainudin, to learn more about their role at Civo. Through this series, we aim to provide you with an overview of the different roles we have at Civo and what advice our team has. You can discover more about our team in our “day in the life of a Go Dev” and “day in the life of an Intern” blog.
This blog will discuss running serverless containers in AWS EKS with Fargate. Why and how we can use this configuration and provides a working example of how to use AWS EKS with Fargate. Recently, a customer reached out with an interesting request. They wanted us to run containers in serverless mode with AWS EKS. Their intention was to use Kubernetes features and run containers in serverless mode. Side note: in EKS you should manage NodeGroups and pay for it.
IoT Device Management Guide The Internet of Things has been raising lots of discussions and debates (of course for the benefits it offers). According to IoT Analytics, the number of connected IoT devices crossed 12 billion in 2020, which was 2 billion more than the estimated devices. Recent trends indicate that this technological transformation will not just be restricted to random “things” but will be ubiquitous, or what few are calling the Internet of Everything.
