.NET Core vs Axon

Overview

.NET Core

Stacks7.0K

Followers2.6K

Votes155

GitHub Stars21.7K

Forks4.9K

Axon

Stacks67

Followers89

Votes0

GitHub Stars3.5K

Forks822

.NET Core vs Axon: What are the differences?

Development Platform: .NET Core is a framework developed by Microsoft for creating cross-platform applications, whereas Axon is a framework designed for building scalable and loosely coupled applications using the CQRS and Event Sourcing patterns.
Supported Programming Languages: .NET Core supports programming languages such as C#, F#, and Visual Basic, while Axon is specifically designed for Java-based applications.
Community Support: .NET Core has a large and active community due to its backing by Microsoft, providing extensive documentation, tutorials, and support forums. In contrast, Axon has a smaller community but is dedicated to providing guidance and assistance for developers using the framework.
Architecture Focus: .NET Core focuses on building a wide range of applications, including web, desktop, cloud, and IoT applications, while Axon is tailored for applications that require complex business logic or event-driven architectures.
License: .NET Core is open-source and free to use, with support for commercial use and contributions from the community, while Axon is also open-source but is governed by the Apache 2.0 license, which has its own set of terms and conditions for usage.
Tooling and Ecosystem: .NET Core offers a comprehensive set of tools, libraries, and extensions through Visual Studio and Visual Studio Code, enabling developers to build, test, and deploy applications efficiently, whereas Axon provides a specific set of tools and integrations for implementing CQRS and Event Sourcing patterns effectively.

In Summary, .NET Core and Axon differ in terms of development platform, supported languages, community support, architecture focus, licensing, and tooling/ecosystem.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on .NET Core, Axon

Anonymous

Dec 16, 2019

Review

There has been a lot of buzz around having PostgreSQL for ASP.NET Core 3.1 web apps. But Configuring Identity Server 4 with PostgreSQL is a real challenge. I've made a simple video to configure the ASP.NET Core 3.1 based Web application that uses AngualrJS as front end with Single Page App capabilities with Identity Server 4 talking to the PostgreSQL database. Check out this Video tutorial on how to do that in detail http://bit.ly/2EkotL5 You can access the entire code here on github http://bit.ly/35okpFj

210k views210k

Comments

Jakub

Jan 2, 2020

Decided

I was researching multiple high performance, concurent//parallel languages for the needs of authentication and authorization server, to be built on microservice architecture and Linux OS. Node.js with its asynchronous behavior and event loop suits the case best. Python Django & Flash turns to be slower and .NET Core & Framework wasn't the best choice for the Linux environment at the time (summer 2018).

I also tested Go lang and Rust, although they didn't meet the quick prototyping criteria as both languages are young and lacking libraries or battle-tested ORM.

377k views377k

Comments

Detailed Comparison

.NET Core	Axon
Cross-platform (supporting Windows, macOS, and Linux) and can be used to build device, cloud, and IoT applications.	Based on architectural principles, such as DDD and CQRS, Axon Framework provides the building blocks to create scalable and extensible applications while maintaining consistency in distributed systems.
Cross-platform; Consistent across architectures; Command-line tools; Flexible deployment; Compatible with .NET Framework, Xamarin and Mono, via .NET Standard; Open source; Supported by Microsoft	Scalability and Performance; Auditability and Transparency; Business Agility; Application and Business Insights
Statistics
GitHub Stars 21.7K	GitHub Stars 3.5K
GitHub Forks 4.9K	GitHub Forks 822
Stacks 7.0K	Stacks 67
Followers 2.6K	Followers 89
Votes 155	Votes 0
Pros & Cons
Pros 30 Perfect to do any backend ( and a fast frontend) stuff 27 Fast 26 Cross-platform 25 Great performance 18 All Platform (Mac, Linux, Windows)	No community feedback yet
Integrations
Linux C# Visual Studio Code Sublime Text .NET Visual Studio ASP.NET Vim Visual Basic F#	MongoDB Kafka Spring Boot Java Spring Framework gRPC Kotlin Spring Cloud Project Reactor

What are some alternatives to .NET Core, Axon?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Related Comparisons

.NET Core vs Axon: What are the differences?

Development Platform: .NET Core is a framework developed by Microsoft for creating cross-platform applications, whereas Axon is a framework designed for building scalable and loosely coupled applications using the CQRS and Event Sourcing patterns.
Supported Programming Languages: .NET Core supports programming languages such as C#, F#, and Visual Basic, while Axon is specifically designed for Java-based applications.
Community Support: .NET Core has a large and active community due to its backing by Microsoft, providing extensive documentation, tutorials, and support forums. In contrast, Axon has a smaller community but is dedicated to providing guidance and assistance for developers using the framework.
Architecture Focus: .NET Core focuses on building a wide range of applications, including web, desktop, cloud, and IoT applications, while Axon is tailored for applications that require complex business logic or event-driven architectures.
License: .NET Core is open-source and free to use, with support for commercial use and contributions from the community, while Axon is also open-source but is governed by the Apache 2.0 license, which has its own set of terms and conditions for usage.
Tooling and Ecosystem: .NET Core offers a comprehensive set of tools, libraries, and extensions through Visual Studio and Visual Studio Code, enabling developers to build, test, and deploy applications efficiently, whereas Axon provides a specific set of tools and integrations for implementing CQRS and Event Sourcing patterns effectively.

In Summary, .NET Core and Axon differ in terms of development platform, supported languages, community support, architecture focus, licensing, and tooling/ecosystem.

.NET Core vs Axon

Overview