What is Axon and what are its top alternatives?
Top Alternatives to Axon
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...
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 is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...
.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...
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 provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. ...
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 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
- Open source15
- Written in Scala and java. Runs on JVM10
- Message broker + Streaming system6
- Avro schema integration4
- Suport Multiple clients2
- Partioned, replayable log2
- Extremely good parallelism constructs1
- Simple publisher / multi-subscriber model1
- Non-Java clients are second-class citizens27
- Needs Zookeeper26
- Operational difficulties7
- Terrible Packaging2
related Kafka posts
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:
- Our Algorithms Tour: https://algorithms-tour.stitchfix.com/
- Our blog: https://multithreaded.stitchfix.com/blog/
- Careers: https://multithreaded.stitchfix.com/careers/
#DataScience #DataStack #Data
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.
- Great libraries1.1K
- Open source795
- Great for apis484
- Great community420
- Great for realtime apps390
- Great for command line utilities295
- Node Modules81
- Uber Simple67
- Great modularity57
- Allows us to reuse code in the frontend56
- Easy to start40
- Great for Data Streaming35
- Non blocking IO24
- Can be used as a proxy17
- High performance, open source, scalable16
- Non-blocking and modular15
- Easy and Fun14
- Easy and powerful12
- Same lang as AngularJS12
- Future of BackEnd11
- Cross platform9
- Mean Stack7
- Great for webapps6
- Easy concurrency6
- Fast, simple code and async5
- Great speed4
- Fast development4
- Its amazingly fast and scalable4
- Control everything4
- Easy to use and fast and goes well with JSONdb's4
- It's fast3
- Easy to use3
- Isomorphic coolness3
- Sooper easy for the Backend connectivity2
- Easy to learn2
- TypeScript Support2
- Scales, fast, simple, great community, npm, express2
- One language, end-to-end2
- Not Python2
- Performant and fast prototyping2
- Blazing fast2
- Great community2
- Less boilerplate code2
- Event Driven1
- Bound to a single CPU46
- New framework every day42
- Lots of terrible examples on the internet35
- Asynchronous programming is the worst29
- Dependency based on GitHub11
- Dependency hell10
- Low computational power10
- Can block whole server easily7
- Very very Slow6
- Callback functions may not fire on expected sequence6
- Unneeded over complication3
- Breaking updates3
- No standard approach1
related Node.js posts
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.
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:
- Rapid development634
- Open source468
- Great community401
- Easy to learn353
- Beautiful code215
- Great packages191
- Great libraries178
- Comes with auth and crud admin panel65
- Great documentation60
- Great for web58
- Great orm37
- Great for api34
- All included27
- Web Apps22
- Used by top startups18
- Easy setup15
- Convention over configuration12
- The Django community9
- Allows for very rapid development with great libraries9
- Great MVC and templating engine6
- King of backend world6
- Its elegant and practical6
- Batteries included5
- Full stack5
- Fast prototyping5
- Easy Structure , useful inbuilt library5
- Easy to develop end to end AI Models5
- Have not found anything that it can't do5
- Very quick to get something up and running4
- Easy to use4
- Great peformance3
- Just the right level of abstraction3
- Full-Text Search3
- Zero code burden to change databases3
- Python community3
- Many libraries3
- Easy to change database manager2
- Node js1
- Underpowered templating25
- Underpowered ORM19
- Autoreload restarts whole server19
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Configuration hell6
- Not as clean and nice documentation like Laravel4
- Not typed3
- Bloated admin panel included3
- Overwhelming folder structure2
- InEffective Multithreading1
related Django posts
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.
- Great mvc11
- Easy to learn3
- Not highly flexible for advance Developers1
- Entity framework is very slow1
related ASP.NET posts
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...
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
- Clean architecture514
- Growing community374
- Composer friendly348
- Open source323
- The only framework to consider for php303
- Quickly develop195
- Dependency injection159
- Application architecture147
- Embraces good community packages134
- Write less, do more62
- Restful routing55
- Orm (eloquent)52
- Artisan scaffolding and migrations47
- Database migrations & seeds47
- Great documentation34
- Awsome, Powerfull, Fast and Rapid26
- Promotes elegant coding25
- Build Apps faster, easier and better25
- Easy to learn, scalability22
- JSON friendly22
- Eloquent ORM21
- Modern PHP21
- Most easy for me21
- Blade Template19
- Based on SOLID12
- Clean Documentation11
- Easy to attach Middleware10
- Convention over Configuration10
- Easy Request Validatin9
- Easy to use8
- Its just wow8
- Get going quickly straight out of the box. BYOKDM8
- Laravel + Cassandra = Killer Framework8
- Less dependencies7
- Friendly API7
- Super easy and powerful7
- Simplistic , easy and faster7
- Great customer support6
- Its beautiful to code in6
- The only "cons" is wrong! No static method just Facades5
- Fast and Clarify framework5
- Active Record5
- Laravel Mix4
- Minimum system requirements4
- Easy views handling and great ORM4
- Laravel Nova3
- Laravel casher3
- Laravel Passport3
- Ease of use3
- Cashier with Braintree and Stripe3
- Laravel Forge and Envoy3
- Laravel Horizon and Telescope3
- Laravel Spark3
- Intuitive usage3
- Heart touch2
- Like heart beat2
- Rapid development2
- Laravel love live long2
- Touch heart artisan2
- Too many dependency28
- Slower than the other two20
- A lot of static method calls for convenience16
- Too many include13
- Does not work well for file uploads in Shared Hosting4
- Too underrated4
- Not fast with MongoDB2
- Difficult to learn1
- Not using SOLID principles1
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.
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.
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
- Android development285
- Necessary for android153
- Android studio127
- Mobile framework85
- Backed by google81
- Eclipse + adt plugin21
- Powerful, simple, one stop environment4
related Android SDK posts
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.
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.
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/
- Powerful and handy135
- Easy setup127
- Lots of "off the shelf" functionalities34
- Cloud Solid29
- Caches well23
- Many receipes around for obscure features21
- Integrations with most other Java frameworks19
- Spring ecosystem is great19
- Fast Performance With Microservices18
- Easy setup, Community Support, Solid for ERP apps13
- One-stop shop13
- Easy to parallelize12
- Easy setup, good for build erp systems, well documented11
- Powerful 3rd party libraries and frameworks11
- Easy setup, Git Integration10
- It's so easier to start a project on spring3
- Heavy weight19
- Annotation ceremony17
- Many config files needed10
- Excellent tools for cloud hosting, since 5.x4
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.
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
- Rapid development850
- Great gems649
- Great community605
- Convention over configuration481
- Great for web349
- Beautiful code344
- Open source311
- Great libraries270
- Active record260
- Easy to learn89
- Easy Database Migrations86
- Makes you happy78
- Great routing62
- Has everything you need to get the job done53
- Great Data Modeling41
- MVC - Easy to start on38
- Easy setup35
- Great caching26
- Ultra rapid development time25
- It's super easy22
- Great Resources17
- Easy to build mockups that work16
- Less Boilerplate14
- API Development7
- Developer Friendly7
- Great documentation6
- Easy REST API creation5
- Great language4
- Haml and sass4
- Easy to learn, use, improvise and update4
- It works2
- Jet packs come standard2
- Easy and fast2
- Convention over configuration1
- Easy Testing1
- It's intuitive1
- Too much "magic" (hidden behavior)22
- Poor raw performance13
- Asset system is too primitive and outdated11
- Heavy use of mixins6
- Bloat in models6
- Very Very slow3
related Rails posts
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.
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