Node-Boot Framework
  • 👋Welcome to Node-Boot
  • 💡Why Node-Boot?
    • No CLI
    • No Boilerplate
    • Standardisation at its core
    • Spring-Boot Features Parity
  • 🥇Mission
  • 🚀Getting Started
  • Letter to Developers
    • 📝Letter to Node.Js Developers
    • 📝Letter to Web3 Developers
    • 📝Letter to Spring-Boot Developers
    • 📝Letter to Node.Js Framework Developers
  • Fundamentals
    • 🧩Architecture
      • Overview
      • Bootstrap
      • Lifecycle
      • Application Context
    • 🪄Core Features
      • Dependency Injection
      • Bean and Configuration
      • Configuration Properties
        • Static Configuration
        • Reading Configuration
        • Writing Configuration
        • Defining Configuration
        • Configuration Properties
      • Controller
        • Available Decorators
        • Custom Decorator
        • Versioning
      • Service
      • Component
      • Logging
      • Error Handling
      • Transactions
        • Transaction Principles
        • Transactions vs Concurrency
        • 🙈Using Transactions
      • Middleware/Interceptors
      • Authorization
      • Marshalling vs Unmarshalling
    • 🗝️Auto-Configuration
    • 🔐Security
  • Servers
    • 🚂Servers Concept
    • 🚃Available Servers
      • Fastify
      • Express
      • Koa
    • 🔌Integrate Server?
  • Starters
    • 🏗️Starters Overview
    • 🎁Available Starters
      • Persistency
      • Validations
      • Actuator
      • Open API
      • Redis
Powered by GitBook
On this page
  1. Why Node-Boot?

Spring-Boot Features Parity

At Node-Boot, we champion the principle of similarity and feature parity with Spring-Boot framework.

We recognise the unparalleled developer experience and robustness that Spring-Boot offers for Spring (Java) developers, and we're committed to providing a framework that mirrors its best practices, concepts, and capabilities for Node.js.

With Node-Boot, Spring-Boot developers can seamlessly transition to the Node.js ecosystem, enjoying the familiarity of their preferred framework while harnessing the power and versatility of Node.js. Our mission is clear: to bridge the gap between Spring-Boot and Node.js, empowering developers to achieve their goals with confidence and ease.

Node-Boot embraces concepts like:

  • Auto-Configuration: Beans and Configuration classes

  • Pluggable HTTP Server

  • Pluggable Dependency Injection

  • Starter Packages (plugins with auto-configuration)

  • Actuator

  • Auto-generated OpenAPI specs and Swagger UI

  • Configuration Properties

  • Data Repositories

  • Transactions support via annotations (decorators)

PreviousStandardisation at its coreNextMission

Last updated 1 year ago

💡