Azure Functions vs Dkron

Overview

Azure Functions

Stacks785

Followers705

Votes62

Dkron

Stacks9

Followers28

Votes0

Azure Functions vs Dkron: What are the differences?

What is Azure Functions? Listen and react to events across your stack. Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

What is Dkron? Distributed, fault tolerant job scheduling system. Dkron is a system service that runs scheduled jobs at given intervals or times, just like the cron unix service but distributed in several machines in a cluster. If a machine fails (the leader), a follower will take over and keep running the scheduled jobs without human intervention.

Azure Functions and Dkron can be categorized as "Serverless / Task Processing" tools.

Some of the features offered by Azure Functions are:

Easily schedule event-driven tasks across services
Expose Functions as HTTP API endpoints
Scale Functions based on customer demand

On the other hand, Dkron provides the following key features:

Executor plugins
Processor plugins
Web UI

🔥 Trending in Serverless on StackShare

AWS Lambda Serverless

Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB

Try it View Docs Alternatives

Try

223

18.8k

Advice on Azure Functions, Dkron

Mark

Nov 2, 2020

Needs adviceon

Microsoft Azure

Need advice on what platform, systems and tools to use.

Evaluating whether to start a new digital business for which we will need to build a website that handles all traffic. Website only right now. May add smartphone apps later. No desktop app will ever be added. Website to serve various countries and languages. B2B and B2C type customers. Need to handle heavy traffic, be low cost, and scale well.

We are open to either build it on AWS or on Microsoft Azure.

Apologies if I'm leaving out some info. My first post. :) Thanks in advance!

133k views133k

Comments

Detailed Comparison

Azure Functions	Dkron
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.	Dkron is a system service that runs scheduled jobs at given intervals or times, just like the cron unix service but distributed in several machines in a cluster. If a machine fails (the leader), a follower will take over and keep running the scheduled jobs without human intervention.
Easily schedule event-driven tasks across services;Expose Functions as HTTP API endpoints;Scale Functions based on customer demand;Develop how you want, using a browser-based UI or existing tools;Get continuous deployment, remote debugging, and authentication out of the box	Executor plugins; Processor plugins; Web UI; Rest API; Job retries; Job chaining; Concurrency control; Historial Metrics; Docker executor; AWS ECS executor; Elasticsearch processor; Advanced Email processor; Embedded storage engine (etcd); Encryption; Web UI Authorization; API Authorization; Dedicated Support
Statistics
Stacks 785	Stacks 9
Followers 705	Followers 28
Votes 62	Votes 0
Pros & Cons
Pros 14 Pay only when invoked 11 Great developer experience for C# 9 Multiple languages supported 7 Great debugging support 5 Can be used as lightweight https service Cons 1 Poor support for Linux environments 1 Sporadic server & language runtime issues 1 Not suited for long-running applications 1 No persistent (writable) file system available	No community feedback yet
Integrations
Azure DevOps Java Bitbucket Node.js Microsoft Azure GitHub Visual Studio Code JavaScript Azure Cosmos DB C#	No integrations available

What are some alternatives to Azure Functions, Dkron?

AWS Lambda

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

Google Cloud Run

A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.

Serverless

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.

Google Cloud Functions

Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

Knative

Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center

OpenFaaS

Serverless Functions Made Simple for Docker and Kubernetes

Nuclio

nuclio is portable across IoT devices, laptops, on-premises datacenters and cloud deployments, eliminating cloud lock-ins and enabling hybrid solutions.

Apache OpenWhisk

OpenWhisk is an open source serverless platform. It is enterprise grade and accessible to all developers thanks to its superior programming model and tooling. It powers IBM Cloud Functions, Adobe I/O Runtime, Naver, Nimbella among others.

Cloud Functions for Firebase

Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics.

AWS Batch

It enables developers, scientists, and engineers to easily and efficiently run hundreds of thousands of batch computing jobs on AWS. It dynamically provisions the optimal quantity and type of compute resources (e.g., CPU or memory optimized instances) based on the volume and specific resource requirements of the batch jobs submitted.