Structure

• Frontend Frontend Layer example, built with Angular
• Global Global Layer layer that can be shared between the backend and the frontend
• Backend Hosting Layer for exposing Application and Domain Services over a multiple transports
• Backend Application Services Layer for composing Domain Services
• Backend Domain Services Layer for encapsulating core domain logic
• Backend Infrastructure Layer packages, for building and supporting the layered architecture

Architecture Overview

Developer Benefits

There are a number of benefits that make NestJs and Angular a very compelling web development stack:

• Core technologies NestJS and Angular are both versatile and highly compatible frameworks, that provide a great developer experience
• Consistent technology and development patterns for both frontend and backend development
  • Results in significant increase in development efficiency
  • TypeScript language for both the backend and frontend
  • Strongly type on both the backend and frontend
  • Leverages the Node JavaScript framework for both backend and frontend development
  • Incredibly similar architecture and design patterns
• Backend framework can be leveraged for other execution contexts, including CLI (example included) or even Desktop
• Leverages fully open source technology
• Hosting options are broad, and flexible, with multiple value-options, and broad native cloud hosting support (including Heroku)

Background

NestJS is a fantastic project, and a pleasure to develop with. However, it is a framework by design, and not a complete production-ready web-application solution. Features such as logging, configuration management, data-base migrations, and even authentication need to be learned, assembled, and configured before they can be used.

This project aims to provide an enterprise-ready web-application skeleton, out-of-the-box, and built on top of the nest-js framework.

Notes

• The Backend can run independently from the CLI
• The CLI requires the Backend to compile and run
• The Frontend can run independently, but requires the Backend to be running to complete requests, including for authentication

Contributions

Contributions are not only welcome, but encouraged. Please help make this better! See the Contributions Guide for details.

Attributions

See the Attributions section.

Companion Libraries

This library is part of a collection of companion tools and libraries under the AbleStack umbrella. All of these libraries share the common goal:

Helping small teams and solo-developers build big ideas rapidly and affordably

To achieve these goals, the following principles are applied:

• Selectively leverage existing open source tools and libraries, where, high quality, open source tools and libraries where possible
  • Curate usage examples, and guidance where available, and create where not available
• Prioritize technology choices that embrace open source
  • PostgreSQL over MSSQL is an example of this
• Avoid technology choices that could result in hosting vendor lock-in
  • ApolloGraphQL over AWS Amplify is an example of this
• Automate wherever possible, from development, through testing, to deployment, monitoring, and maintenance
  • Codegen from strongly types schemas is a good example of this.
• Where needed, develop high quality, open source tools and libraries to augment and automate existing open source tooling and libraries

Readme Navigation

Further details on each of the systems contained in this project can be found via the following links:

• Overview
• Frontend
• Backend
• CLI
• DevOps