Ask HN: How is your JavaScript based backend organized?

📰 Hacker News · horsecaptin

Learn how to organize a JavaScript-based backend by exploring frameworks and tools for data migrations, deployments, and more

intermediate Published 8 Dec 2017

Action Steps

Explore JavaScript frameworks like NestJS, Express.js, and Hapi to find a suitable replacement for Ruby on Rails
Use tools like TypeORM or Sequelize for Object-Relational Mapping (ORM)
Implement data migrations using libraries like db-migrate or migrate-js
Configure deployments using Docker and container orchestration tools like Kubernetes
Set up background tasks using libraries like Bull Queue or Agenda.js
Design APIs using RESTful architecture or GraphQL

Who Needs to Know This

Backend developers and full-stack developers transitioning from Ruby on Rails to JavaScript can benefit from understanding how to organize their codebase and leverage existing frameworks and tools

Key Insight

💡 JavaScript has a wide range of frameworks and tools to help organize backend development, from data migrations to deployments and beyond

Full Article

I come from a Ruby on Rails background. It is great - working with Rails has had two huge upsides for me. First, the framework means there is a good way to do almost everything. Two, it makes me think about problems and the solutions generally fit elegantly into the framework. Now, I'm sure there are Rails like frameworks for full-stack Javascript development. I'd love to hear about how you organize things like: - Data migrations. - Deployments. - ORM - Background tasks. - APIs - Multiple language support in front-end templates. etc..etc.. Do most people roll their own back-kend framework? As an aside, whats the state of server-side template rendering? Is that industry practice?

Read full article → ← Back to Reads