Alternatives to Axon logo

Alternatives to Axon

Kafka, Node.js, Django, ASP.NET, and Laravel are the most popular alternatives and competitors to Axon.
55
68
+ 1
0

What is Axon and what are its top alternatives?

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.
Axon is a tool in the Frameworks (Full Stack) category of a tech stack.
Axon is an open source tool with 2.5K GitHub stars and 681 GitHub forks. Here’s a link to Axon's open source repository on GitHub

Top Alternatives to Axon

  • Kafka

    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • Node.js

    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. ...

  • Django

    Django

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

  • ASP.NET

    ASP.NET

    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...

  • Laravel

    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. ...

  • Android SDK

    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. ...

  • Spring Boot

    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. ...

  • Rails

    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. ...

Axon alternatives & related posts

Kafka logo

Kafka

15.7K
14.8K
573
Distributed, fault tolerant, high throughput pub-sub messaging system
15.7K
14.8K
+ 1
573
PROS OF KAFKA
  • 122
    High-throughput
  • 116
    Distributed
  • 87
    Scalable
  • 81
    High-Performance
  • 65
    Durable
  • 36
    Publish-Subscribe
  • 19
    Simple-to-use
  • 15
    Open source
  • 10
    Written in Scala and java. Runs on JVM
  • 6
    Message broker + Streaming system
  • 4
    Avro schema integration
  • 2
    Suport Multiple clients
  • 2
    Robust
  • 2
    KSQL
  • 2
    Partioned, replayable log
  • 1
    Fun
  • 1
    Extremely good parallelism constructs
  • 1
    Simple publisher / multi-subscriber model
  • 1
    Flexible
CONS OF KAFKA
  • 27
    Non-Java clients are second-class citizens
  • 26
    Needs Zookeeper
  • 7
    Operational difficulties
  • 2
    Terrible Packaging

related Kafka posts

Eric Colson
Chief Algorithms Officer at Stitch Fix · | 21 upvotes · 2M views

The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

For more info:

#DataScience #DataStack #Data

See more
John Kodumal

As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

See more
Node.js logo

Node.js

125K
103.6K
8.4K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
125K
103.6K
+ 1
8.4K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 795
    Open source
  • 484
    Great for apis
  • 474
    Asynchronous
  • 420
    Great community
  • 390
    Great for realtime apps
  • 295
    Great for command line utilities
  • 81
    Node Modules
  • 80
    Websockets
  • 67
    Uber Simple
  • 57
    Great modularity
  • 56
    Allows us to reuse code in the frontend
  • 40
    Easy to start
  • 35
    Great for Data Streaming
  • 31
    Realtime
  • 26
    Awesome
  • 24
    Non blocking IO
  • 17
    Can be used as a proxy
  • 16
    High performance, open source, scalable
  • 15
    Non-blocking and modular
  • 14
    Easy and Fun
  • 12
    Easy and powerful
  • 12
    Same lang as AngularJS
  • 11
    Future of BackEnd
  • 10
    Fast
  • 9
    Fullstack
  • 9
    Scalability
  • 9
    Cross platform
  • 8
    Simple
  • 7
    Mean Stack
  • 6
    Great for webapps
  • 6
    Easy concurrency
  • 5
    Friendly
  • 5
    Fast, simple code and async
  • 5
    React
  • 4
    Great speed
  • 4
    Fast development
  • 4
    Its amazingly fast and scalable
  • 4
    Control everything
  • 4
    Easy to use and fast and goes well with JSONdb's
  • 4
    Typescript
  • 4
    Scalable
  • 3
    It's fast
  • 3
    Easy to use
  • 3
    Isomorphic coolness
  • 2
    Sooper easy for the Backend connectivity
  • 2
    Easy to learn
  • 2
    TypeScript Support
  • 2
    Scales, fast, simple, great community, npm, express
  • 2
    One language, end-to-end
  • 2
    Javascript2
  • 2
    Not Python
  • 2
    Performant and fast prototyping
  • 2
    Blazing fast
  • 2
    Great community
  • 2
    Less boilerplate code
  • 2
    Easy
  • 1
    Lovely
  • 1
    Event Driven
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 42
    New framework every day
  • 35
    Lots of terrible examples on the internet
  • 29
    Asynchronous programming is the worst
  • 23
    Callback
  • 16
    Javascript
  • 11
    Dependency based on GitHub
  • 10
    Dependency hell
  • 10
    Low computational power
  • 7
    Can block whole server easily
  • 6
    Very very Slow
  • 6
    Callback functions may not fire on expected sequence
  • 3
    Unneeded over complication
  • 3
    Unstable
  • 3
    Breaking updates
  • 1
    No standard approach

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 1.7M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 39 upvotes · 4.2M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
Django logo

Django

26.6K
23.5K
3.8K
The Web framework for perfectionists with deadlines
26.6K
23.5K
+ 1
3.8K
PROS OF DJANGO
  • 634
    Rapid development
  • 468
    Open source
  • 401
    Great community
  • 353
    Easy to learn
  • 263
    Mvc
  • 215
    Beautiful code
  • 210
    Elegant
  • 193
    Free
  • 191
    Great packages
  • 178
    Great libraries
  • 68
    Restful
  • 65
    Comes with auth and crud admin panel
  • 65
    Powerful
  • 60
    Great documentation
  • 58
    Great for web
  • 44
    Python
  • 37
    Great orm
  • 34
    Great for api
  • 27
    All included
  • 22
    Web Apps
  • 21
    Fast
  • 18
    Used by top startups
  • 16
    Clean
  • 15
    Easy setup
  • 15
    Sexy
  • 12
    Convention over configuration
  • 10
    ORM
  • 9
    The Django community
  • 9
    Allows for very rapid development with great libraries
  • 6
    Great MVC and templating engine
  • 6
    King of backend world
  • 6
    Its elegant and practical
  • 5
    Mvt
  • 5
    Batteries included
  • 5
    Full stack
  • 5
    Fast prototyping
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Easy to develop end to end AI Models
  • 5
    Have not found anything that it can't do
  • 4
    Very quick to get something up and running
  • 4
    Easy to use
  • 4
    Easy
  • 4
    Cross-Platform
  • 3
    Map
  • 3
    Great peformance
  • 3
    Scaffold
  • 3
    Just the right level of abstraction
  • 3
    Modular
  • 3
    Full-Text Search
  • 3
    Zero code burden to change databases
  • 3
    Python community
  • 3
    Many libraries
  • 2
    Easy to change database manager
  • 1
    Node js
CONS OF DJANGO
  • 25
    Underpowered templating
  • 19
    Underpowered ORM
  • 19
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Admin
  • 7
    Not nodejs
  • 6
    Configuration hell
  • 4
    Not as clean and nice documentation like Laravel
  • 3
    Python
  • 3
    Not typed
  • 3
    Bloated admin panel included
  • 2
    Overwhelming folder structure
  • 1
    InEffective Multithreading

related Django posts

Dmitry Mukhin

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
ASP.NET logo

ASP.NET

21.4K
6.7K
14
An open source web framework for building modern web apps and services with .NET
21.4K
6.7K
+ 1
14
PROS OF ASP.NET
  • 11
    Great mvc
  • 3
    Easy to learn
CONS OF ASP.NET
  • 1
    Not highly flexible for advance Developers
  • 1
    Entity framework is very slow

related ASP.NET posts

Greg Neumann

Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

See more

Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

ASP.NET / Node.js / Laravel. ......?

Please guide us

See more
Laravel logo

Laravel

20.4K
16.2K
3.5K
A PHP Framework For Web Artisans
20.4K
16.2K
+ 1
3.5K
PROS OF LARAVEL
  • 514
    Clean architecture
  • 374
    Growing community
  • 348
    Composer friendly
  • 323
    Open source
  • 303
    The only framework to consider for php
  • 202
    Mvc
  • 195
    Quickly develop
  • 159
    Dependency injection
  • 147
    Application architecture
  • 134
    Embraces good community packages
  • 62
    Write less, do more
  • 55
    Restful routing
  • 52
    Orm (eloquent)
  • 47
    Artisan scaffolding and migrations
  • 47
    Database migrations & seeds
  • 36
    Awesome
  • 34
    Great documentation
  • 26
    Awsome, Powerfull, Fast and Rapid
  • 25
    Promotes elegant coding
  • 25
    Build Apps faster, easier and better
  • 22
    Easy to learn, scalability
  • 22
    JSON friendly
  • 21
    Eloquent ORM
  • 21
    Modern PHP
  • 21
    Most easy for me
  • 20
    Test-Driven
  • 19
    Blade Template
  • 18
    Beautiful
  • 13
    Security
  • 12
    Based on SOLID
  • 11
    Simple
  • 11
    Clean Documentation
  • 11
    Cool
  • 10
    Easy to attach Middleware
  • 10
    Convention over Configuration
  • 9
    Easy Request Validatin
  • 8
    Easy to use
  • 8
    Its just wow
  • 8
    Simpler
  • 8
    Get going quickly straight out of the box. BYOKDM
  • 8
    Laravel + Cassandra = Killer Framework
  • 8
    Fast
  • 7
    Less dependencies
  • 7
    Friendly API
  • 7
    Super easy and powerful
  • 7
    Simplistic , easy and faster
  • 6
    Great customer support
  • 6
    Its beautiful to code in
  • 5
    The only "cons" is wrong! No static method just Facades
  • 5
    Fast and Clarify framework
  • 5
    Active Record
  • 5
    Php7
  • 5
    Speed
  • 5
    Easy
  • 4
    Composer
  • 4
    Laravel Mix
  • 4
    Minimum system requirements
  • 4
    Easy views handling and great ORM
  • 4
    Eloquent
  • 4
    Laragon
  • 3
    Laravel Nova
  • 3
    Laravel casher
  • 3
    Laravel Passport
  • 3
    Ease of use
  • 3
    Cashier with Braintree and Stripe
  • 3
    Laravel Forge and Envoy
  • 3
    Laravel Horizon and Telescope
  • 3
    Laravel Spark
  • 3
    Intuitive usage
  • 2
    Heart touch
  • 2
    Like heart beat
  • 2
    Rapid development
  • 2
    Laravel love live long
  • 2
    Touch heart artisan
  • 2
    Scout
CONS OF LARAVEL
  • 42
    PHP
  • 28
    Too many dependency
  • 20
    Slower than the other two
  • 16
    A lot of static method calls for convenience
  • 13
    Too many include
  • 10
    Heavy
  • 7
    Bloated
  • 6
    Laravel
  • 5
    Confusing
  • 4
    Does not work well for file uploads in Shared Hosting
  • 4
    Too underrated
  • 2
    Not fast with MongoDB
  • 1
    Difficult to learn
  • 1
    Not using SOLID principles

related Laravel posts

I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

Need help deciding technology stack. Thanks.

See more
Antonio Sanchez

Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

See more
Android SDK logo

Android SDK

19.7K
14.8K
786
An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
19.7K
14.8K
+ 1
786
PROS OF ANDROID SDK
  • 285
    Android development
  • 153
    Necessary for android
  • 127
    Android studio
  • 85
    Mobile framework
  • 81
    Backed by google
  • 26
    Platform-tools
  • 21
    Eclipse + adt plugin
  • 4
    Powerful, simple, one stop environment
  • 2
    Free
  • 2
    Больно
CONS OF ANDROID SDK
    Be the first to leave a con

    related Android SDK posts

    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 858.7K views

    We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

    Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

    We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

    You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

    See more
    Sezgi Ulucam
    Developer Advocate at Hasura · | 7 upvotes · 667.5K views

    I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

    The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

    See more
    Spring Boot logo

    Spring Boot

    17.1K
    15K
    914
    Create Spring-powered, production-grade applications and services with absolute minimum fuss
    17.1K
    15K
    + 1
    914
    PROS OF SPRING BOOT
    • 135
      Powerful and handy
    • 127
      Easy setup
    • 118
      Java
    • 86
      Spring
    • 82
      Fast
    • 42
      Extensible
    • 34
      Lots of "off the shelf" functionalities
    • 29
      Cloud Solid
    • 23
      Caches well
    • 21
      Many receipes around for obscure features
    • 20
      Productive
    • 20
      Modular
    • 19
      Integrations with most other Java frameworks
    • 19
      Spring ecosystem is great
    • 18
      Fast Performance With Microservices
    • 17
      Auto-configuration
    • 16
      Community
    • 13
      Easy setup, Community Support, Solid for ERP apps
    • 13
      One-stop shop
    • 12
      Cross-platform
    • 12
      Easy to parallelize
    • 11
      Easy setup, good for build erp systems, well documented
    • 11
      Powerful 3rd party libraries and frameworks
    • 10
      Easy setup, Git Integration
    • 3
      It's so easier to start a project on spring
    • 3
      Kotlin
    CONS OF SPRING BOOT
    • 19
      Heavy weight
    • 17
      Annotation ceremony
    • 10
      Many config files needed
    • 8
      Java
    • 5
      Reactive
    • 4
      Excellent tools for cloud hosting, since 5.x

    related Spring Boot posts

    Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

    Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

    See more
    Praveen Mooli
    Engineering Manager at Taylor and Francis · | 14 upvotes · 2M views

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

    See more
    Rails logo

    Rails

    15.4K
    10.6K
    5.4K
    Web development that doesn't hurt
    15.4K
    10.6K
    + 1
    5.4K
    PROS OF RAILS
    • 850
      Rapid development
    • 649
      Great gems
    • 605
      Great community
    • 481
      Convention over configuration
    • 417
      Mvc
    • 349
      Great for web
    • 344
      Beautiful code
    • 311
      Open source
    • 270
      Great libraries
    • 260
      Active record
    • 106
      Elegant
    • 89
      Easy to learn
    • 86
      Easy Database Migrations
    • 78
      Makes you happy
    • 74
      Free
    • 62
      Great routing
    • 53
      Has everything you need to get the job done
    • 41
      Great Data Modeling
    • 38
      MVC - Easy to start on
    • 38
      Beautiful
    • 35
      Easy setup
    • 26
      Great caching
    • 25
      Ultra rapid development time
    • 22
      It's super easy
    • 17
      Great Resources
    • 16
      Easy to build mockups that work
    • 14
      Less Boilerplate
    • 7
      API Development
    • 7
      Developer Friendly
    • 6
      Great documentation
    • 5
      Quick
    • 5
      Easy REST API creation
    • 4
      Intuitive
    • 4
      Great language
    • 4
      Haml and sass
    • 4
      Easy to learn, use, improvise and update
    • 2
      It works
    • 2
      Jet packs come standard
    • 2
      Easy and fast
    • 2
      Legacy
    • 2
      Metaprogramming
    • 1
      Convention over configuration
    • 1
      Easy Testing
    • 1
      Cancan
    • 1
      It's intuitive
    CONS OF RAILS
    • 22
      Too much "magic" (hidden behavior)
    • 13
      Poor raw performance
    • 11
      Asset system is too primitive and outdated
    • 6
      Heavy use of mixins
    • 6
      Bloat in models
    • 3
      Very Very slow

    related Rails posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Russel Werner
    Lead Engineer at StackShare · | 30 upvotes · 1.5M views

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more