Diagrid Offers Free Trial Edition of Dapr SaaS Service

Diagrid today announced it is offering a free 30-day trial of Conductor Enterprise, a software-as-a-service (SaaS) edition of the open source Dapr runtime platform for deploying microservices on Kubernetes clusters.

The overall goal is to make it simpler to provide development teams with initial access to a platform that makes it simpler to build cloud-native applications using a framework originally developed by Microsoft that is now being advanced under the auspices of the Cloud Native Computing Foundation (CNCF).

Step 1 of 7

14%

Which of the following best describes how you currently monitor and manage systems across your hybrid cloud environment?(Required)

Multiple separate tools for different environments

Multiple separate tools for different monitoring and management functions

Single consolidated dashboard

Custom built monitoring and management solution

No full monitoring and management solution

Don’t know

How valuable would it be for your monitoring and management solution to incorporate predictive analytics to help you identify and address system issues that are critical and not waste time or effort working through all the data and “noise” that is not critical?(Required)

Extremely valuable

Moderately valuable

Somewhat valuable

Slightly valuable

Not valuable

How do you most typically address potential system issues BEFORE they impact your operations?(Required)

Automated workflows and playbooks to remediate potential issues as soon as they are detected

An orchestrated response process that leverages automation, AI, and human expertise to rapidly respond to potential issues

Advanced monitoring tools such as predictive analytics and anomaly detection to proactively identify and address potential issues

Respond to issues as they arise, using manual processes and troubleshooting techniques

A combination of automated remediation, orchestrated response, and/or proactive monitoring to address potential system issues

Don’t know

Other

What methods does your organization use to control and monitor cloud/IT spending?(Required)

Centralized procurement processes

Pre-approved budget thresholds

Automated cost monitoring tools

Department-level spending controls

Regular cost audits and reviews

Cloud cost optimization platform

Approval workflows for resource provisioning

Native financial operations tools provided by the cloud provider

No formal controls in place

Don’t know

Other

Please specify:

Which methods do you rely on most to detect security vulnerabilities in your systems?(Required)

Automated scanning tools

Manual assessments

Vendor notifications

Threat modeling (for early detection)

None of these

Don’t know

Other

Please specify:

What are the TWO most common ways you prioritize vulnerabilities to address within your environment?(Required)

Based on potential impact

Based on exploitability

Regulatory compliance requirements

Based on CVSS scores

Risk-based analysis of multiple factors

First-in-first-out approach

No formal prioritization process

Don’t know

How do you typically handle system updates and security patches?(Required)

Automated updates and patches

Manually review and apply updates and patches on a regular schedule

A combination of automation and manual review

Apply updates and patches on an as-needed basis.

Outsourced update and patch management

No defined process

Don’t know

Other

Δ

Diagrid CEO Mark Fussell said rather than each developer having to write, for example, publish and subscribe code needed to integrate microservices, the Dapr framework provides a reusable alternative that can support multiple programming languages.

The SaaS platform provided by Diagrid takes that capability a step further by eliminating the need to update Dapr, he added. Instead, Conductor Enterprise provides IT teams with a centralized management console for managing multiple instances of Dapr running on Kubernetes clusters, he added. In addition to automating the deployments of updates to the Dapr runtime, the SaaS platform monitors more than 150 Dapr metrics in real-time to optimize resource utilization and ensure cybersecurity, noted Fussell.

A graph created by Diagrid also provides a dynamic overview of services and infrastructure components employing the Dapr framework.

Dapr is being used today by more than 10,000 developers building cloud-native applications. It’s not clear how much momentum Dapr has in terms of continued adoption. Still, as more Kubernetes clusters are deployed across hybrid IT environments, it’s only a matter of time before developers build more distributed applications. As a runtime capable of spanning those environments, Dapr presents IT teams with a way to build and deploy those applications more easily.

Less clear within IT organizations is who will champion the adoption of a platform such as Dapr. Still, with the rise of platform engineering as a methodology for managing DevOps workflows at scale, it’s apparent more organizations are trying to centralize application development workflow management. There are, of course, multiple paths those teams might pursue to achieve that goal, but a case for including a framework capable of supporting multiple programming languages, including Java and Python, can be made. Otherwise, IT teams will need to provide access to either a similar framework for each programming language employed or support multiple equivalents of custom integration code created by individual developers that they will then need to maintain, noted Fussell.

In general, it’s only a matter of time before more development teams realize they are essentially writing the same integration code over and over again multiple times. At a time when the pressure to deliver cloud-native applications on time is only increasing, Dapr provides a method to accelerate the application development process by eliminating the need to write the same integration code over again. The challenge, as always, is finding someone willing to take on the task of maintaining instances of Dapr that will naturally begin to multiply as more developers decide they would rather spend their time writing business logic versus integration code that, in the final analysis, is yet another tedious task that all too often is simply getting in the way.