The latest News and Information on DevOps, CI/CD, Automation and related technologies.
The reasons to move to Kubernetes are many and compelling. This post doesn’t make the case that you should migrate, but assumes you have already decided that you want to. When you’re clear on what you want to do and why you want to do it, the questions of “When?” and “How?” become your focus. What follows centers on the question of how to approach making Kubernetes the platform on which your workloads thrive.
Today, you probably wouldn’t blink at the idea of involving security in your development process. In fact, “shifting security left” has become so commonplace in the security industry, that there are conferences and job titles dedicated to SecOps (or DevSecOps or SecDevOps *eye roll emoji*). Yet, it wasn’t that long ago that the massive transition to this mindset took place.
Over the past few months, we published a number of articles showing how to snap desktop applications written in different languages – Rust, Java, C/C++, and others. In each one of these zero-to-hero guides, we went through a representative snapcraft.yaml file and highlighted the specific bits and pieces developers need to successfully build a snap. Today, we want to diverge from this journey and focus on the server side of things.
Apache Flink is an open source framework, written in Java and Scala, for stateful processing of real-time and batch data streams. Flink offers robust libraries and layered APIs for building scalable, event-driven applications for data analytics, data processing, and more. You can run Flink as a standalone cluster or use infrastructure management technologies such as Mesos and Kubernetes.