As we discussed in the previous section API versioning isn’t as simple as having running different services to handle the different versions, whereby each service processes each version independently of the other. With Kubernetes, your controller watches the state of an object in etcd, that stored object is versioned to a single value (i.e. only 1 version is ever stored at a time), and when you set-up a watch on the resource whichever version you ask for is the version you will get.
Therefore, when writing a k8s operator, there are a set of requirements and conventions we need to be aware of to ensure that we’re able to progress the software development lifecycle of the API specification and the controller versions in a robust manner.
When working with Kubernetes, we all frequently make calls to retrieve or create resources. Whenever we run kubectl apply
or kubectl get
, we are requesting that an object be added to or retrieved from the database. When we write a manifest, we always include an apiVersion
attribute but what does this mean and how does Kubernetes respond to different values?
The landscape of AI and compute-intensive applications underwent a significant transformation with Google Cloud's latest innovation. On August 21, 2024, Google Cloud launched the public preview of Cloud Run with GPUs, a feature that integrated the power of NVIDIA L4 GPUs into the serverless Cloud Run platform.
This new offering is more than just an incremental upgrade—it represented a major advance in how developers could harness the power of AI inference and handle resource-intensive tasks with greater efficiency on Google Cloud.
Tired of AI responses that miss the mark? Struggling to get the results you need? The key to unlocking AI's true power is in your hands – through crafting the perfect prompt. Mastering this skill will revolutionise how you brainstorm, create, and tackle challenges.
At Mesoform, we're passionate about AI's potential to transform your workflow and creative process. We're here to guide you on your AI journey, empowering you with the knowledge and tools to harness its full capabilities. Get ready to unleash new levels of productivity, creativity, and innovation in your business.
Bridging the Gap: DevOps, SRE, and the Cybersecurity Imperative
The tech world is a fast-paced arena, and staying ahead of the curve demands seamless collaboration. Development (Dev) and Operations (Ops) teams have long recognised the power of joining forces in a DevOps approach. Now, Site Reliability Engineering (SRE) adds another layer to this dynamic duo, with a laser focus on building reliable and scalable systems. But in this age of digital transformation, there's a third player demanding equal attention: Cybersecurity.
Mesoform's State of the Union report dives deep into this interconnected landscape. We're not just talking about tools and technologies – this report explores the people and the cultures that make these systems tick. From how teams are structured and how they communicate to the very foundations of their technology choices, we'll uncover the hidden links between DevOps, SRE, and the ever-present need for security.
If you're in the IT world, you've probably heard whispers of "platform engineering". But is it just another buzzword, or is it something more? Let me tell you, this is one trend you don't want to miss.
In the fast-paced and interconnected digital landscape, the complexity of managing diverse IT systems and networks has surged. To tackle this challenge, organisations are increasingly turning to centralised monitoring, a robust approach that provides a unified and comprehensive view of their entire infrastructure. Centralised monitoring involves consolidating the monitoring of various components, systems, cloud environments and applications into a centralised platform, offering real-time insights and analytics. This shift from siloed monitoring to a centralised model is driven by the need for enhanced visibility, proactive issue detection, and overall operational efficiency.
In the dynamic world of digital innovation, securing a scalable app deployment remains a formidable challenge. Our recent work for a crypto trading startup mirrors this pursuit: the quest for a robust, lightweight, and highly secure architecture for a trading app. This challenge reflects the industry's demand for fortified security amidst a landscape rife with potential threats. In this particular project, Mesoform was employed, not only to provide site reliability, cloud and DevOps engineering but a complete technical architecture and technology management over the whole project. Guiding platform engineering, software engineering and DevOps, as well as architecture and UI design, our holistic approach aimed to optimise project performance and functionality in order to deploy a Crypto Trading App for a crypto trading startup.
In this particular project, Mesoform was employed, not only to provide site reliability, cloud and DevOps engineering but a complete technical architecture and technology management over the whole project. Guiding platform engineering, software engineering and DevOps, as well as architecture and UI design, our holistic approach aimed to optimise project performance and functionality in order to deploy a Crypto Trading App for ProTraders.
In this particular project, Mesoform was employed, not only to provide site reliability, cloud and DevOps engineering but a complete technical architecture and technology management over the whole project. Guiding platform engineering, software engineering and DevOps, as well as architecture and UI design, our holistic approach aimed to optimise project performance and functionality in order to deploy a Crypto Trading App for a crypto trading startup.