41–50 of 122 posts
Spring with Spring Boot in Java. Batteries included and easy to setup and get going. A statically typed language to catch errors at compile time. Easy to deploy by building an uberjar. Great dependency management and builds with Gradle/Maven and built-in support for pretty much any common database and message queue.
It's super fast, C# is mad fun to develop in, and now it runs on Linux. We've even started deploying production sites to CentOS-based VPSes.
Spring Framework on backend -> ultra power and speed, especially if you go cloud and microservices route Angular 1 on fronted -> easy enough to learn quickly, feels good to use and is powerful with great support and add-ons. Looking to start learning angular2 Will learn elixir and phoenix for some realtime and websocket stuff.
As long as you're happy with your microservices needing at least a gigabyte of memory each. My current project has ~15 Spring microservices, and with two instances each and blue-green deployment, we need 60 gigabytes just to be in business.
Escher.jl - http://escher-jl.org
Yes, I primarily use it because it's Julia and I am really enjoying Julia, but it's also a very interesting take on a modern web framework for a modern language (even if it is a bit rough around the edges).
TypeScript, because its a fast compiler and has the best typechecker support and typings collection for existing front-end libraries, so there is almost no need to wrap anything.
React, because its conceptually simple, has wide community support and I get TypeScript's type checking inside the TSX templates too, unlike in Vue and most other frameworks.
MobX, because it needs less boilerplate than Redux, plays better with TypeScript than immutable.js, is really easy to make performant (lots of observer components + computed properties) and its intuitive to developers coming from Angular, knockout or Vue.
On the backend: TypeScript, Node, bluebird, node-sql and PostgreSQL
TypeScript, because it makes it easy to write end-to-end-typechecked programs if the backend language is the same as the frontend. The client and server can both claim to implement the same interface, and then its easy to see if any changes violate that contract. Additionally, server-side rendering with React is simpler.
Node, because its reasonably fast without thinking too much about it. The only pitfall are accidentally cpu-bound tasks, but in practice those are a problem rarely and I'm working on a tool to detect and report them: https://github.com/spion/long-task-detector
Another thing missing in node are better streams. A promise-friendly version of pull-stream would fix that.
Bluebird, because its fast and provides a great debugging experience with long stack traces
PostgreSQL, because it can go very far for many things before you need something else.
node-sql, because its an SQL query builder for node which can be made typesafe with TypeScript, and because query builders often beat ORM spaghetti in performance and maintainability in the long run.
For newer/bleeding-edge I use Go with Vue.js on the frontend. I like Vue's simplicity and community - It's the only frontend framework that made sense to me and I was able to be productive in in a relatively short time. Go on the backend because it's clean, fast and stable.
At the risk of self-promotion, check out my weekend project - https://github.com/zohararad/bee-gorm-graphql (Golang on the backend, Vue on the frontend)
Love the simplicity, speed and power. Huge ecosystem and fast rampup.