devopsy.kinsta.cloud

Category: Cloud Management

LaunchDarkly Extends Scope and Reach of Feature Management Platform

LaunchDarkly this week, via a Galaxy update to its feature management platform, added a range of tools to address everything from making it simpler to deliver specific capabilities to end users after an application has been deployed to providing increased observability of workflows.

In addition, the company revealed alliances with GitHub, Bitrise, Snowflake, Twilio and Sentry that make it possible to invoke the feature management platform from within platforms provided by these environments.

Jonathan Nolen, senior vice president of engineering for LaunchDarkly, said the goal is to make it possible to integrate a software-as-a-service (SaaS) platform for managing features both before and after applications are developed with DevOps workflows.

The Galaxy Product Release update specifically adds a Segment Builder tool to make it easier to define what capabilities will be enabled for various groups of users and an Engineering Insights Hub to track velocity and quality metrics.

Other additions include a Release Assistant tool to build pre-defined, repeatable paths for progressive rollouts, a Release Guardian tool to quickly identify and remediate operational regressions, a Migration Assistant tool to help move software from one platform to another and a Mobile Release Optimizations tool.

Finally, LaunchDarkly has added a Funnel Experiments capability to its existing Product Experimentation tool to measure and optimize user behavior.

As more organizations start to deliver different tiers of digital services at varying price points, there is a clear need to be able to restrict access to those digital services. Application development teams have, of course, been employing feature management since the 1970s to isolate the development of various components into a branch that can be worked on and tested without impacting the primary build the application is based on. Feature management, in effect, enables development teams to experiment with adding new capabilities in a way that doesn’t disrupt the application. When a project is completed, that branch is then usually merged into the primary build or can be deployed as a microservice that might be invoked via an application programming interface (API) by other modules with the application or another external application.

At the core of that capability are what are known as feature flags, also known as feature toggles or feature switches, that make it possible to dynamically turn services on or off based on who is accessing them. Rather than being limited to the application development process, those feature flags are now being employed in production environments to enable the continuous delivery of multiple types of digital services to various classes of users of an application. A feature flag management platform enables an organization to keep track of all the flags being employed to keep the overall application environment consistent.

LaunchDarkly is making a case for a SaaS platform that can be used to centrally manage features across multiple workflows as an alternative to employing feature management capabilities embedded with a continuous integration/continuous delivery (CI/CD) platform.

Each organization will need to decide for itself how best to manage features based on how many DevOps platforms they may employ. But it’s clear that feature management is now playing a much larger role in surfacing a wide range of application experiences at a time when organizations are more dependent on software than ever.

October 26, 2023
Stacklet Applies Generative AI to Simplify Cloud Governance

Stacklet today provided early access to a Jun0 tool that leverages generative artificial intelligence (AI) to improve cloud governance and reduce costs.

Stacklet CEO Travis Stanfield said the goal is to make it possible to automatically surface recommendations and implement policies using a mix of large language models (LLMs) trained using data collected via the company’s Stacklet AssetDB database.

Accessed via a natural language interface, Jun0 makes it possible to declaratively govern cloud computing environments via text-based queries to generate policies that can be implemented as code; that eliminates the need for specialized programming expertise, he added.

IT teams can use text to launch queries pertaining to any operations, cost, security and compliance issues and then visually test the policies created as part of a dry run before implementing them at scale. In effect, Jun0 substantially reduces the level of expertise required to successfully manage cloud computing environments by making it simpler to create governance policies, noted Stanfield.

DevOps teams are generally tasked with making sure cloud computing environments are optimally managed using policies that are usually implemented as code within a DevOps workflow. Implementing policy-as-code, however, typically involves mastering a domain-specific programming language. Stacklet is now making a case for a higher level of abstraction that eliminates the need to master yet another programming language to govern cloud computing environments.

It’s still early days as far as the adoption of generative AI is concerned within DevOps workflows, but it’s already clear that implementing best practices is about to become substantially easier. In essence, DevOps practices are about to become democratized in a way that reduces the cognitive load required to implement them. In addition to increasing the number of application environments a DevOps team may be able to effectively manage, generative AI will make DevOps accessible to a wider range of organizations that previously would not have been able to hire and retain software engineers.

Many of those software engineers should also be able to spend more time addressing more complex issues rather than, for example, writing scripts to ensure that only certain classes of workloads are allowed to run on a particular cloud service within a period of time which results in lower costs.

Unfortunately, DevOps teams are already playing catch-up when it comes to having access to generative AI tools. Developers are already taking advantage of generative AI tools to create more code faster. As that code moves through DevOps pipelines, it’s apparent the overall size of the codebase that DevOps teams are being required to manage is only going to increase. Most organizations are not going to be able to hire a small army of software engineers to manage that codebase, so the tooling provided to existing DevOps teams will need to improve. The issue now is narrowing the gap between now and when next-generation AI tools are made generally available. One way or another, however, it’s clear that the way DevOps is managed will never be the same again.

October 25, 2023
Survey Surfaces Benefits of Applying AI to FinOps

A survey of 200 enterprise IT decision-makers published this week found organizations that have infused artificial intelligence (AI) into financial operations (FinOps) workflows to reduce IT costs are 53% more likely to report cost savings of more than 20%.

Conducted by the market research firm Foundry on behalf of Tangoe, a provider of tools for managing IT and telecommunications expenses, the survey found organizations that embraced FinOps without any AI capabilities averaged less than 10% in cost savings.

The top three drivers for adopting FinOps/cloud cost management programs are the need to increase cloud resource production and performance (70%), reduce budgets (60%) and rising costs (58%), and simpler overall program management (50%), the survey found. Major benefits included productivity savings (46%), cost savings (43%) and reduced security risks (43%). Nearly two-thirds of respondents cited service utilization and right-sizing of services as another reason to embrace FinOps.

FinOps describes a methodology for embedding programmatic controls within DevOps workflows to reduce costs. In the face of increased economic headwinds, IT leaders are looking to reduce cloud computing costs, but it’s turning out to be more challenging than many of them anticipated. Cloud infrastructure is typically provisioned by developers using infrastructure-as-code (IaC) tools with little to no supervision. The reason for this is developers have long argued that waiting for an IT team to provision cloud infrastructure took too long. Developers would be more productive if they just provisioned cloud infrastructure themselves.

However, after ten years of cloud computing, it’s become apparent there are a lot of wasted cloud infrastructure resources. Developers who don’t pay the monthly bills for cloud services tend to view available infrastructure resources as essentially infinite. It’s usually not until someone from the finance department starts raising cost concerns that developers even become aware there might be an issue.

The challenge is that adopting FinOps best practices is not quite as easy as it might seem. In fact, more than half (54%) of survey respondents cited challenges in building the right process and human support systems for FinOps into workflows that have been in place for years.

Chris Ortbals, chief product officer for Tangoe, said the simplest path to FinOps is to rely on a software-as-a-service (SaaS) platform designed from the ground up to leverage AI to help IT teams manage cloud computing and telecommunications expenses both before and after applications are deployed. Each DevOps team will ultimately need to determine how much they will implement metrics to foster more efficient consumption of cloud computing resources. The more aware of those costs DevOps teams are, the more likely that better decisions about what types of workloads should be run where and, just as importantly in the age of the cloud, at what time, given all the pricing options provided.

Developers, of course, tend to jealously guard their prerogatives. Convincing them to give up their ability to provision cloud infrastructure on demand is going to be a challenge, at least until someone makes it plain how much all those cloud instances wind up costing the organization each and every month.

October 19, 2023
Latest DORA Report Highlights Importance of DevOps Culture

A 2023 Accelerate State of DevOps Report published today by the DevOps Research and Assessment (DORA) team at Google Cloud found teams with generative cultures composed of people who felt included on their team have 30% higher organizational performance than organizations without a generative culture.

The report was based on a global survey of 36,000 IT professionals and tracked deployment frequency, change lead time, culture, change failure rates and failed deployment recovery times.

Overall, the survey found that while just under a third of respondents were successful in terms of their ability to deploy on demand (31%) and keep remediation efforts after deployments to 5% (33%), only 18% had lead times for changes of less than one day, while only 17% had a failed deployment recovery time of less than an hour.

This is an area where DevOps teams appear to need the most amount of help; nearly two-thirds (64%) of software releases or updates required some level of remediation after deployment, according to the report.

Nathen Harvey, developer advocate for DORA and Google Cloud, said the one area most underappreciated when it comes to improving performance is documentation. High-quality documentation leads to 25% higher team performance, the survey found.

DevOps teams that rely on the public cloud also benefited from a 22% increase in infrastructure flexibility, resulting in 30% higher organizational performance, noted Harvey.

The survey also noted that, as far as reliance on artificial intelligence (AI) to automate DevOps workflows is concerned, it’s still early. But most respondents are, at the very least, experimenting with one or more use cases.

In general, the management of DevOps will soon be very different as more AI capabilities are leveraged to eliminate bottlenecks and reduce toil. The immediate challenge is developers are benefiting more from AI than software engineers, which is resulting in more code starting to simultaneously move through DevOps pipelines. There is little doubt that in the months ahead there will be increased reliance on AI to manage pipelines at greater scale. In the meantime, it will be increasingly difficult to manage codebases that are steadily getting larger as developers become more productive.

At the same time, more organizations are embracing platform engineering as a methodology for centralizing the management of DevOps workflows at levels of scale that previously were difficult to achieve.

Hopefully, the combination of platform engineering and AI will result in less overall burnout among DevOps teams. In the short term, the burnout issue may become more challenging to address as the amount of code being created increases.

In the longer term, the results of the DORA survey may be substantially different next year as AI and platform engineering are employed more widely. The current survey results are not substantially different than in previous years, in the sense that DevOps teams are still challenged by many of the same issues.

Of course, as important as it might be to improve those metrics, the most important thing any DevOps team should focus on is developer productivity which, despite the existence of DevOps pipelines, remains relatively low.

October 5, 2023
Something is Amiss in the Open Source World
You don’t have to be a psychic to grok that the winds of change are blowing hard in the open source world. For the last few months, I’ve seen hints and heard whispers about a new direction for what I believe is the most passionate and enthusiastic community in tech. I think we are about to sail off into unchartered territory—and it will be interesting to see what the repercussions are.

Of course, this will all play out against the backdrop of continued layoffs and belt-tightening in the broader tech sector. Before I detail what I think are the telltale signals of change, let me state that I am and have always been a big supporter of open source software. I firmly believe we live in a golden age for open source software, which I call the “Foundation era of open source.” At a time when 90% plus of organizations use open source software, many of the leading open source projects are under the domain of not-for-profit foundations (NFPs) such as the Linux Foundation, the Apache Foundation, etc. This allows multiple commercial companies who might otherwise compete with each other to work in coop-etition. This has, in many ways, enabled this golden age of open source. Prior to the Foundation era of open source, there were two prior dominant models. Initially, there was what I call the “Cathedral and Bazaar era,” named after the great book by Eric Raymond. This was a time of idealistic notions of “pure” open source, unsullied by commercial aspirations. To me, Dr. Richard Stallman embodied that time; if you were to make an analogy to history, it was akin to the 1960s era in the U.S.

From that era, let’s zoom to sometime in the early 2000s when we moved to what I call the “Big Brother era” of open source. In this era, open source projects were owned and managed by one vendor, for all intents and purposes. The project could have a vibrant community, but ultimately, it was the managing vendor or “Big Brother” who reaped most of the rewards. This made it difficult for multiple tool vendors to support the same project and stifled progress.

The dawn of the foundation era of open source changed all that, and we have seen transformational growth as a result. But nothing lasts forever—and I think the king of the hill may be on the way down. Why do I say this? Here are several events/trends I’ve noticed recently that lead me to believe this. Some of these things I was told in confidence, so I cannot reveal names to protect the innocent.
1. The move away from “pure” open source licenses. Over the last few months, several pillars of the open source world have moved away from accepted open source licensing. Red Hat has done so with Red Hat Enterprise Linux (RHEL) and now Hashi has, as well. Now, to some, this change is subtle and it’s not a big deal. Only paying customers get access to source code. The overwhelming majority of users never look at the source code anyway. Nevertheless, this is a huge red flag for the community—the accepted licenses and a core tenant of open source, that source code is available to everyone, are no longer being used.
2. Diminishing corporate financial support for open source communities and foundations. I guess this was to be expected in hard economic times. The path to profits from supporting open source foundations, projects and communities can sometimes be more of a dotted line than direct. And a dotted line doesn’t usually work when the bean counters are involved. In looking to cut expenses, these are low-hanging fruit.
3. Closing foundations. This is a natural result of the economic strife. Foundations may operate as not-for-profits, but without operating funds, foundations can’t operate. Generally, foundations get a lot of mileage from volunteers. However, volunteers can only go so far before hard costs are involved. Also, volunteers are able to volunteer because their corporate employers empower them to do so. When their employers pull back the funding for those activities, the volunteers have to do what they can to earn a living. I have heard of at least one NFP foundation forced to cease or curtail operations due to corporate sponsor funds drying up.
4. Orphaned projects. Again, this is a direct result of number two, above. With the foundations closing and supporting funds drying up, I know of at least two bellwether open source projects that are in danger of becoming orphaned. Both of these projects boast huge community numbers and dominate their markets. The fact is though, that supporting a major project costs hundreds of thousands of dollars. While millions of community members may use a project and support it, they don’t contribute dollars. Dollars that pay for hosting, infrastructure and other hard costs. Coughing up a few hundred grand to support a project is a bridge too far for some companies in the current economic climate.
What does this mean for open source software and you? Well, in the near term, if you are just a consumer of open source software, probably not much will change day-to-day. You may have to cough up some money if you want access to source code or support from the community. Bigger picture, though, is the winds of change are blowing. I think we are going to see more companies taking a Hashi-type approach to protecting their source code. This will result in more forks of open source projects. However, my experience is that most open source forks don’t succeed (with some notable exceptions—like Jenkins forked from Hudson). Companies who are building businesses around open source models will be the most at risk. I think an open core business model may be the best bet for an open source vendor. I think the future of NFPs as the stewards of open source may become a bit cloudy (no pun intended). What will take its place or fill the void? That remains to be seen.

For the record I was never a fan of that old Irish proverb, “May you live in interesting times.” This kind of upheaval is a little too interesting for me. But one thing I have learned in 30 years in tech (and more than that in life) is that change is constant. You can embrace it and thrive or shrivel and die.
October 5, 2023
Avoiding Cloud Lock-In Amidst Potential Regulatory Change

At the end of my street, there’s a beautiful and much-admired garden with vibrant flowers and a well-manicured lawn. Next to this splendid garden is an abandoned vacant lot, long-neglected and overgrown with weeds. Every time I walk by, I think about how this neglected space could be transformed into something magnificent (like this garden), but no one wants to take responsibility for it. Similarly, many CIOs and CTOs have “discarded vacant lots” to deal with in their own work lives: The problem of cloud lock-in.

Cloud lock-in can be a significant headache for business leaders. Even the UK’s communications sector regulator, Ofcom, has expressed concerns about the issue. Earlier this year, Ofcom announced that it would refer the UK cloud market for investigation to the Competition and Markets Authority, highlighting barriers to interoperability and concerns about high egress fees charged by the cloud hyperscalers.

But organizations shouldn’t just wait (and hope) for regulators to solve this problem. As a true believer in harnessing the full benefits of the cloud, I propose two practical ways to combat cloud lock-in.

The Upside of a Technical Approach

The first option is straightforward: Have an honest conversation with your cloud service account leader. Express your concerns about lock-in and negotiate more favorable terms and conditions. This approach might yield some results, but it’s not a guaranteed success. So, there’s a more effective strategy: Adopt a technical approach that empowers you to avoid vendor lock-in altogether, without costing you an arm and a leg.

Imagine that, instead of trying to turn your neglected space into a garden alone, you could access a ready-made gardening community, where multiple people work together to create something amazing. The same principle applies to cloud databases. Rather than relying exclusively on one hyperscaler’s technology stack, you can opt for platforms that offer portability and flexibility across different cloud providers.

Let’s consider databases, a critical underlying component of many mission-critical business applications. Each cloud hyperscaler will offer a range of SQL, NoSQL, and graph database options, which cater to various types and scales of technical problems. The challenge is to avoid getting locked into a single cloud stack, which hinders your ability to switch between clouds if and when needed.

One viable solution is to choose “vanilla Postgres” – the basic open source version of PostgreSQL available from postgres.org or any cloud provider. This will certainly provide initial flexibility, but you are likely to encounter limitations as your application grows and requires enterprise-level features.

The real benefit of the cloud lies in modernizing your data layer to fully exploit cloud-native features like scalability and resilience.

To achieve this, you need databases that run across different public clouds and share common APIs. Born-in-the-cloud technologies, designed from the ground up for cloud environments, offer the most flexibility and benefits.

Examining your current cloud vendor’s offerings is natural, as you’re already on their platform. However, keep in mind that these services are customized to their specific cloud environment only, so this could limit your future growth. If you decide to change cloud providers or adopt a multi-cloud strategy, moving across the cloud database “matrix” can be cumbersome due to the inconsistent APIs.

If you were restricted to a single set of gardening tools when trying to transform that discarded space into a beautiful community garden, it would be nearly impossible and would not be fit for purpose.

You need to realize that these services and their functionality will always need to be customized in some way to the specific cloud environment. AWS’s fully managed relational database engine, Aurora, is compatible with MySQL and PostgreSQL, but it was specifically designed to run on Amazon. This means it can’t run on-prem, and it certainly won’t work in GCP (Google’s cloud).

As a consequence, you will have to make time-consuming and costly changes to your application to accommodate a bespoke version of PostgreSQL that will run efficiently in the cloud environment of your hyperscaler partner. You’re going to be locked into that version of the application because it can’t really work anywhere else. The same applies to the Google equivalent of vanilla Postgres (CloudSQL for Postgres), or the Microsoft version (Azure PostgreSQL).

If you truly want a multi-cloud strategy, you need to consider how you go, for example, from mid-range Google to low-end Amazon. Scaling is much discussed, but surely one of the main selling points of cloud is that you can go down as easily as you go up.

The Business Advantages of Multi-Cloud are in Reach

To achieve the advantages of multi-cloud, you need to consider databases that offer common APIs and portability across clouds. There are several open source PostgreSQL-based database options available, which enable you to keep your cloud database options open and avoid the trap of cloud vendor lock-in.

The wait for regulatory intervention might be long and uncertain. Taking proactive steps now to mitigate cloud lock-in is crucial.

Adopt a scalable open source PostgreSQL option to immediately enjoy many of the benefits of multi-cloud. Embracing this strategy now can spare you potential panic moves when and if regulatory changes come into play.

By freeing your business from the shackles of cloud lock-in, you can unleash the true potential of multi-cloud environments. Just like that “discarded vacant lot” waiting to be transformed into a beautiful garden, your applications can blossom in a multi-cloud ecosystem, which allows you to easily scale up or down and enjoy the best that each cloud provider has to offer.

So, don’t wait for someone else to fix the problem. Take action today and start cultivating your multi-cloud future.

October 3, 2023
Best Practices for DevOps in the Hybrid Cloud

In rеcеnt years, various tools, technologies and frameworks have еmеrgеd with thе goal of enhancing flеxibility, performance and scalability. Traditional monolithic approaches have been replaced by more modular methods like microservices and nano-services. Additionally, the rise of cloud computing has led to on-prеmisеs software being replaced by cloud еnvironmеnts that offer a wide array of advantages and capabilities that were previously unavailable.

Bеing able to optimize spееd and efficiency through the adaptation of cloud settings is a vital capability. To leverage cloud-bursting capabilities and also safeguard their applications and data, businеssеs can embrace a hybrid cloud strategy combined with DеvOps. In this article, we will dеlvе into bеst practices for implеmеnting DеvOps in a hybrid cloud sеtting.

What is a Hybrid Cloud Environment?

A hybrid cloud, which combines on-premises and cloud computing modеls, allows you to harness the benefits of both approaches. Hybrid cloud computing allows businеssеs to blеnd their own on-prеmisеs infrastructurе with thе powеr and flеxibility of cloud computing. This approach allows them to optimize their current infrastructure while also benefiting from the scalability and cost efficiency offered by public cloud environments.

By lеvеraging thе strеngths of both, companies can optimizе their opеrations for scalability and flеxibility and еnhancе sеcurity for thеir applications and data. One notablе advantage of hybrid cloud еnvironmеnts is their ability to adapt rеsourcе capacity to mееt еvolving workload dеmands rapidly.

A hybrid cloud offers flexibility and cost optimization to businesses. With a hybrid cloud, enterprises can scale up their resources and adapt to changing needs, much like a public cloud. At the same time, it allows them to retain control over sensitive data and critical applications stored on-site.

By adopting a hybrid cloud environment, organizations gain enhanced data control and the ability to flexibly allocate workloads based on evolving business needs. Organizations can achieve improved flexibility, enhanced security and regulatory compliance by adopting a hybrid cloud model.

What are the Benefits?

Here are the benefits of a hybrid cloud:

Cost-effectiveness: The cloud offers a cost-effective solution for deploying workloads. When using the cloud, an organization does not have to spend much money to purchasе additional infrastructure. Moreover, most cloud environments provide support for a pay-as-you-go pricing model, which implies you only have to pay for what you consume.

Avoids Vendor Lock-in: Companies often face the challenge of becoming too dependent on one cloud provider during the transition to the cloud, making it difficult to switch to another provider if it becomes necessary to do so. However, by adopting a hybrid model and specifically migrating to a platform that supports multiple providers, companies can mitigate this risk and avoid being locked into one vendor.

Improved Developer Productivity: By deploying a hybrid cloud platform, developers will be able to significantly enhance their productivity. With this approach, developers can leverage Agile and DevOps methodologies more efficiently and deploy their applications across multiple cloud infrastructures simultaneously.

Infrastructure Efficiency: A hybrid cloud offers development and IT operations teams enhanced and smooth control over resources. Organizations can also leverage cloud services and combine them with data stored in the cloud or on-premises infrastructure to create more value through the hybrid cloud.

Better compliance and security: Hybrid clouds offer significant benefits for business growth and acceleration. They enable faster product development cycles, promote innovation and expedite time to market. Additionally, they facilitate prompt response to customer feedback and allow for the delivery of applications in closer proximity to customers. Hybrid clouds also facilitate the integration of new services from third-party providers.

Cloud-bursting: One valuable feature of hybrid cloud environments is called cloud bursting, which enables organizations to easily increase their resource capacity to meet varying work demands.

An Overview of Hybrid Cloud Architecture

A typical hybrid cloud architecture comprises of the following components:

On-Premises Infrastructure: This refers to your privately owned physical infrastructure that can be used for storage, network, host servers, etc.

Private Cloud: Generally speaking, a private cloud is an environment that is dedicated solely to the use of a single organization. It can be hosted either internally within the organization’s own premises or externally, but it is securely protected and not accessible to the general public.

Public Cloud: The term public cloud refers to a computing model in which services such as compute, storage, deployment, etc. is provided by third-party providers as a fully managed service over the internet.

Cloud Management Platform: A cloud management platform is responsible for managing the operation and allocation of computing resources across various cloud platforms. It also helps businesses effectively use their hybrid cloud environments.

Orchestration and Automation Tools: Streamlining tasks such as resource provisioning and data synchronization across different environments requires the use of orchestration and automation tools. These tools are crucial in ensuring efficiency and seamless operations.

Best Practices for DevOps in the Hybrid Cloud

Albeit the benefits it provides, successfully implementing DevOps in a hybrid cloud requires you to adhere to certain best practices:

Monitoring: Ensure your on-premises and cloud environments are monitored and managed effectively by using the right tools. These tools offer a comprehensive view of your resources, regardless of their hosting location.

Infrastructure-as-Code (IaC): Use tools like CloudFormation, Terraform or ARM to automate infrastructure provisioning and management. IaC ensures that infrastructure is built consistently and reliably.

Containerization: Container technologies such as Docker and container orchestration platforms like Kubernetes abstract the underlying infrastructure and make moving applications between on-premises and the cloud easier.

Centralized logging: Make sure you have a centralized solution for metrics, logs and traces (like ELK Stack, Prometheus and/or Grafana) that can collect data from both the platform and the cloud environment.

Automation: From CI/CD pipelines to infrastructure deployment, it’s critical to ensure that processes are automated by leveraging tools like GitLab CI, GitHub Actions and/or Jenkins.

Security: You should consistently implement a robust security strategy. Consider the unique security requirements of a hybrid system, such as security of data transfer between disk and the cloud, encryption at rest and in transit and consistent identity and access management.

Performance: Understand latency and bandwidth issues when transferring data between disk and the cloud. Choose the right architecture (such as edge computing) and optimize your applications to minimize these issues.

Data management and integration: You should understand where your data comes from and pay attention to data gravity. You should also link applications and data sources on the server and in the cloud to ensure smooth data flow.

Application architecture: You should design cloud-agnostic, modular and flexible applications. A microservices architecture often works well for hybrid cloud environments.

Disaster Recovery and Backup: Take advantage of both on-premises and cloud resources to establish a robust disaster recovery and backup strategy.

Administration and policy management: You should enforce consistent policies across both environments using policy-as-code by leveraging tools such as Open Policy Agent (OPA).

Training and skills development: Note that hybrid clouds require knowledge across multiple platforms. Ensure your team is trained and has the skills to manage and operate a hybrid environment.

Budget and cost management: You should monitor costs on the server and in the cloud. Tools such as AWS Cost Explorer, Azurе Cost Management and third-party solutions can provide insight into where your money is going.

Communication and collaboration: Although there are challenges and obstacles, you should encourage open communication and team collaboration.

Regular reviews and audits: Review your architecture, tools and procedures to ensure they align with business goals and are as efficient as possible.

What are the Challenges?

Despite its many advantages, hybrid cloud also comes with some challenges. These challenges arise from the complexities of managing multiple environments and integrating them together. Here are the key challenges of hybrid cloud at a glance:

Security Concerns: Hybrid cloud models can pose security vulnerabilities, particularly if there is inconsistent implementation of security protocols across different environments. It is important to properly secure data that moves between private and public environments to mitigate potential risks.

Data Transfer Costs: When moving data between private and public clouds, it’s important to consider the potential costs involved, particularly when dealing with large volumes of data. Being mindful of these expenses is essential when designing hybrid solutions.

Data Sovereignty and Compliance: You must ensure that data complies with regional and industry-specific regulations when it is stored or processed in multiple locations, including public clouds in different regions.

Latency Issues: One of the challenges that may arise when implementing cloud-based applications is the integration with existing legacy systems. This can be a problem, especially for applications that require real-time or high-performance capabilities.

Vendor lock-in: Vendor lock-in can still be a challenge even with a hybrid approach, especially if organizations heavily depend on proprietary tools or services from a specific cloud provider, making it difficult to migrate or integrate with other platforms.

Skills gap: One challenge in managing and operating a hybrid cloud is the potential for a skills gap, since you’ll need a diverse range of skills, such as knowledge of both on-premises and cloud technologies. To address this, organizations may need to provide training or hire new talent with the necessary expertise in both areas.

Monitoring: Achieving visibility and effective monitoring can be challenging when resources are spread across multiple environments. It often requires specialized tools or platforms to achieve end-to-end visibility and monitor effectively.

Governance and Policy Management: Although it is crucial for maintaining security and compliance, it can be challenging to implement consistent governance and policy management across both private and public clouds.

Cost Management and Optimization: While a hybrid cloud can provide cost benefits, it can also be difficult to track and manage costs across multiple platforms. This requires ongoing monitoring and the implementation of optimization strategies.

Network Connectivity: To achieve secure, reliable and fast connectivity between on-premises and cloud environments, a well-designed network infrastructure is essential. This may involve additional investments in network services or infrastructure to ensure seamless connectivity.

How Hybrid Cloud Supports DevOps Culture

Here’s how hybrid cloud supports DеvOps culture:

Automation: Automation plays a crucial role in both hybrid cloud and DеvOps. By utilizing tools and services provided by cloud providers, automation еnablеs the provisioning, scaling, and management of infrastructure. This aligns with the core principles of DеvOps, which include automated installation, integration, and utilization.

Flexibility: Unlike with a single platform or tool, DevOps teams have the freedom to select the most suitable services and platforms from various cloud providers and incorporate them into their own solutions.

Cost Efficiency: DevOps teams can achieve cost efficiency by using public cloud resources for temporary workloads like test environments or short-term projects. Your teams can optimize their costs by only paying for the resources they actually use, thereby optimizing the amount of money they spend on those resources.

Fast deployment of resources: The fast provisioning and de-provisioning of resources are crucial in a DevOps culture. Hybrid cloud allows for rapid deployment of environments, supporting the iterative and dynamic nature of DevOps practices.

Collaboration: Hybrid cloud solutions often include collaboration tools and platforms that promote effective communication and teamwork, aligning with the collaborative culture of DevOps.

Continuous Integration and Continuous Delivery (CI/CD): Hybrid cloud provides tools and platforms that support CI/CD pipelines and enable consistent and continuous integration, testing and transition to production (delivery/deployment).

Service Integration: Many cloud providers provide a wide range of services, including machine learning and databases, as part of their cloud offerings. Using these services will allow you to seamlessly integrate them into your applications, fostering a culture of continuous improvement and innovation.

Monitoring and feedback: Hybrid clouds provide robust monitoring, logging and analytics tools that offer valuable insights into application performance and user experiences.

Regulatory compliance: With a hybrid cloud approach, IT teams can maintain the security and compliance of sensitive data and applications by housing them in a private cloud or controlled environment. This way, organizations can meet their compliance and security standards effectively.

Conclusion

A hybrid cloud combines on-premises infrastructure with cloud computing, offering scalability, flexibility and improved security for applications and data. A hybrid cloud infrastructure should be more flexible than a traditional cloud to meet changing requirements. Therefore, businesses with hybrid cloud capabilities can adapt more quickly to business and technological changes.

Businesses can leverage several benefits by implementing DevOps practices in a hybrid cloud environment, such as improved agility, faster release cycles, enhanced scalability and better collaboration. With a hybrid cloud setup, companies can leverage the strengths of both on-premises infrastructure and cloud computing models to achieve scalability and flexibility.

October 3, 2023
Dell Taps Microsoft to Simplify Hybrid Cloud Computing

Dell Technologies, in collaboration with Microsoft, today unveiled a platform that tightly integrates an on-premises IT environment with the Azure cloud.

Caitlin Gordon, vice president of multi-cloud product management for Dell Technologies, said the Dell APEX Cloud Platform for Microsoft Azure is the first instance of a hybrid cloud computing platform designed specifically to address that requirement using a Premier Solution of the Microsoft Azure Stack hyperconverged infrastructure (HCI) platform that Microsoft added to its portfolio today.

The Premier Edition of Microsoft Azure Stack HCI makes available an instance of that platform that provides a more turnkey management experience than the existing editions, said Gordon.

In the face of increased economic headwinds, more organizations are looking to lower the total cost of managing IT by reducing the number of control planes that need to be managed. Each platform that an IT team typically supports today has its own control plane that requires IT staff to manage it. Reducing the number of control planes creates an opportunity to reduce the total headcount currently required to manage multiple IT platforms.

It also serves to streamline workflows in a way that enables DevOps teams to reduce the current level of friction encountered when managing multiple IT platforms, noted Gordon.

At the core of Microsoft’s approach to hybrid cloud computing that Dell is embracing is Arc, a management framework that makes it possible to manage Azure cloud instances alongside on-premises IT environments. In terms of the ability to manage hybrid cloud computing environments, Microsoft is significantly more advanced than any other cloud service provider, said Gordon.

It’s not clear whether IT organizations are embracing HCI platforms running an instance of the same core stack of software that Microsoft relies on to provide Azure services. If IT organizations expect to lower the cost of managing IT, there is no doubt they will need to modernize on-premises IT infrastructure. The older the platform, the more expensive it becomes to automate using various third-party frameworks.

Regardless of the approach, IT teams need to reconcile the need to invest in automating workflows that span multiple IT platforms. Over time, those investments will reduce the total cost of IT, but getting the required funding to start that process will require IT teams to make a strong case for increasing the return on investment (ROI).

In the meantime, the number of workloads running both in the cloud and at the network edge is only going to increase. At the same time, the bulk of existing workloads continue to run in local data center environments. Most IT teams will be required to find additional ways to automate the management of all those environments simply because the cost of adding additional IT staff to manage highly distributed computing environments as scale will otherwise be prohibitive.

As such, the issues that IT teams are facing today may be a matter of not if the management of IT will become more automated but how soon.

September 26, 2023
Oracle Previews Latest Java 21 Innovations

Oracle today made generally available a Java 21 edition and provided early access to more than 15 proposed enhancements to the Java development kit (JDK).

Those enhancements were announced at an Oracle CloudWorld 2023 conference, including support for virtual threads to improve overall throughput and adding support for a vector application programming interface (API) that makes it simpler to build Java applications that involve artificial intelligence (AI) models.

Georges Saab, senior vice president of Oracle Java Platform and chair of the OpenJDK governing board, said the goal is to streamline access to the latest innovations that will be added to future versions of Java.

Specifically, via Project Amber, JDK 21 delivers improvements such as support for string Templates, record Patterns, pattern Matching for switch, unnamed Patterns and variables and unnamed classes and instance main methods.

In addition to the Vector API, Project Panama adds a Foreign Function & Memory API. Project Loom, in addition to virtual threads, adds scoped values and structured concurrency support.

There is also a more efficient garbage collection mechanism being proposed.

Oracle is committing to offering long-term support for Java 21 for at least eight years to encourage organizations to start working with this version of Java today. Oracle is also making available a Java Playground, an online sandbox on the Oracle Cloud Infrastructure (OCI) service where developers can create Java code using this edition without needing a local runtime or integrated development environment (IDE).

In general, Java has been experiencing a renaissance after more organizations began contributing to projects once the core platform became available under an open source OpenJDK license. In fact, the Java community is now adopting many concepts pioneered in other programming languages. That enables organizations to, for example, drive digital business transformation initiatives that depend on the modernization of legacy applications. As part of those efforts, the rate at which Java applications are being deployed in the cloud has substantially increased.

Despite the number of alternative programming languages, many enterprise IT organizations remain committed to Java. Rather than opting to retrain developers, it’s simply been more cost-effective to enable developers to continue to build applications using a programming language they already know.

Many organizations are currently in the process of shifting to Java 17. It’s not clear how many organizations will skip Java 17 and jump to Java 21 from previous versions of Java, but it’s clear Oracle is committed to making the lag time between moving from previous versions of Java to Java 21 much shorter.

Most organizations will find themselves continuing to deploy Java applications everywhere from the network edge to the cloud. These applications will be written in a programming language that has persevered for more than two decades and continues to evolve and mature for the next era of application development.

September 19, 2023
Buildkite Acquires Packagecloud to Streamline DevOps Workflows

Buildkite Pty Ltd today revealed it has acquired Packagecloud as part of an effort to tightly integrate package management tools with its continuous integration/continuous delivery (CI/CD) platform.

Buildkite CEO Keith Pitt said the goal is to reduce the level of friction that exists between providers of third-party package management tools and CI/CD platforms that DevOps teams are today required to address themselves.

There is no shortage of package management tools used to configure, install and update software, but the level of integration between these tools and CI/CD platforms has not historically been very high. The acquisition of Packagecloud will result in a package manager becoming a first-class citizen within the context of a CI/CD platform, said Pitt.

Buildkite will maintain the existing support Packagecloud provides for platforms such as Jenkins, but the acquisition will streamline DevOps workflows and improve overall developer productivity, he added.

In the months ahead, Buildkite will also add a range of tools to better enable DevOps teams to achieve that goal, said Pitt. In addition, the company plans to add tools to streamline the management of compliance processes as regulations pertaining to application development are becoming more stringent, he added.

It’s not clear how much IT organizations are reevaluating their CI/CD platforms to improve developer productivity, but platform engineering as a methodology to centralize the management of DevOps workflows is gaining traction. Those efforts promise to reduce the total cost of implementing DevOps at scale and improve developer productivity by making the scaffolding required to build applications more readily accessible. Today, too many developers are spending time managing developer environments rather than writing actual code.

The challenge, of course, is convincing developers—who tend to jealously guard their tool prerogatives—to embrace a platform engineering methodology and cede control over the development environment to a centralized team.

One way or another, developer productivity needs to improve as more organizations encounter economic headwinds. Developers are the most expensive resource any organization has, so improving the rate at which high-quality code is created will always be imperative, noted Pitt.

Today, organizations depend on software to drive revenue. Investors are assessing senior leaders within those organizations on their ability to deliver quality software in a timely fashion. Each new application and subsequent software update now has a direct impact on the profitability of the organization. As such, tolerance for legacy approaches to building software that require more time and effort is dropping.

The issue, as always, is that switching from one software development platform to another is an expensive proposition, so many organizations may find themselves supporting a mix of legacy and modern platforms. The challenge becomes defining the pace at which that migration occurs as new applications are created and legacy applications are continuously updated.

September 19, 2023