Need advice about which tool to choose?Ask the StackShare community!
We actually initially wrote a lot of networking code in Kotlin but the complexities involved prompted us to try and compile NodeJS for Android and port over all the networking logic to Node and communicate with node over the Java Native Interface.
This turned out to be a great decision considering our battery usage fell by 40% and rate of development increased by a factor of 2.
As a small team, we wanted to pick the framework which allowed us to move quickly. There's no option better than Rails. Not having to solve the fundamentals means we can more quickly build our feature set. No other framework can beat ActiveRecord in terms of integration & ease-of use. To top it all of, there's a lot of attention paid to security in the framework, making almost everything safe-by-default.
Hey guys,
My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!
Pros of Deno
- Typescript12
- Secure10
- Open source8
- Javascript5
- Formatting5
- Testing5
- Great std library5
- Easy Config2
- ESM2
Pros of Node.js
- Npm1.4K
- Javascript1.3K
- Great libraries1.1K
- High-performance1K
- Open source789
- Great for apis477
- Asynchronous467
- Great community414
- Great for realtime apps385
- Great for command line utilities290
- Node Modules77
- Websockets75
- Uber Simple65
- Great modularity53
- Allows us to reuse code in the frontend53
- Easy to start38
- Great for Data Streaming33
- Realtime29
- Awesome25
- Non blocking IO23
- Can be used as a proxy16
- High performance, open source, scalable15
- Non-blocking and modular14
- Easy and Fun13
- Same lang as AngularJS12
- Easy and powerful11
- Future of BackEnd10
- Fast9
- Cross platform8
- Scalability8
- Mean Stack6
- Fullstack6
- Simple6
- Easy concurrency5
- Great for webapps5
- Easy to use and fast and goes well with JSONdb's4
- Friendly4
- React4
- Fast, simple code and async4
- Typescript4
- Its amazingly fast and scalable3
- Isomorphic coolness3
- Great speed3
- Scalable3
- Control everything3
- Fast development3
- One language, end-to-end2
- Scales, fast, simple, great community, npm, express2
- TypeScript Support2
- Easy to learn2
- Easy to use2
- It's fast2
- Less boilerplate code2
- Blazing fast2
- Not Python2
- Performant and fast prototyping2
- Sooper easy for the Backend connectivity2
- Great community2
- Easy1
- Lovely1
- Event Driven0
- Javascript20
Sign up to add or upvote prosMake informed product decisions
Cons of Deno
- Still in early development2
- Bad Rust plugin support1
Cons of Node.js
- Bound to a single CPU46
- New framework every day37
- Lots of terrible examples on the internet33
- Asynchronous programming is the worst28
- Callback22
- Javascript16
- Dependency based on GitHub11
- Dependency hell10
- Low computational power10
- Can block whole server easily7
- Callback functions may not fire on expected sequence6
- Very very Slow6
- Unneeded over complication3
- Breaking updates3
- Unstable3
- No standard approach1