The Vanilla framework has a history of being released very infrequently. Sometimes it has been months between releases, which made the upgrade process often hard and time-consuming. One of the reasons for that was a manual and a quite time-consuming release process. Over several weeks earlier this year, we’ve been working on various improvements that helped us release more frequently and reliably.
In part 1 we will talk about the industrial applications and benefits that 5G and fast compute at the edge in the form of ‘smart cell towers’ will bring to AI products. In part 2 we will go deeper into how you can benefit from this new opportunity. Part 3 will focus on the key technical barriers that 5G and Edge compute remove for AI applications.
People working in digital enterprises will have no doubt noticed that customers have an insatiable appetite for new features and updates, with next to zero tolerance if digital services are performing poorly – or not at all. To thrive and survive in the digital era, it’s become an imperative for organizations to innovate at an unprecedented pace.
Kubernetes offers scalability and reliability for your container-based applications. Combine this with GKE, and you now eliminate the need to install or operate clusters on your own. A huge plus to using GKE is that you now will be running Kubernetes in a GCP environment, therefore you can utilize all the handy integrations Google has to offer. Codefresh simplifies the process even more, by automating the process of getting your code built, tested, and deployed.
There are many reasons why you may want to use Artifactory as your Maven repository. For example, it allows tagging Maven artifacts with custom properties, so that they can later be found based on specific criteria. It stores build metadata about your artifacts, and allows controlling the repositories used by the Maven build, without modifying the pom file. In this post, I’d like to focus on one specific advantage, Maven deployments in Jenkins.
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.
