LogoLogo
  • Technical Direction
  • Technical overview
    • Technical Implementation
    • API Design Guide
      • Data Definitions and Standards
      • Data Transfer Objects
      • Documentation
      • Environments
      • Error Handling
      • Example API Service
      • GraphQL Naming Conventions
      • Methods
      • Naming Conventions
      • Once Only Principle
      • Pagination
      • Resource Oriented Design
      • REST Request
      • REST Response
      • Security
      • Versioning
    • Ísland.is Public Web Data Flow
    • Code Reviews
    • Code Standards
    • Monorepo
    • Project Management
    • Teamwork
    • Architectural Decision Records
      • Use Markdown Architectural Decision Records
      • Use NX
      • Continuous Integration
      • CSS
      • Branching and Release Strategy
      • Error Tracking and Monitoring
      • What API Management Tool to Consider
      • Viskuausan Static Site Generator
      • Use OAuth 2.0 and OpenID Connect As Protocols for Authentication and Authorization
      • Unified Naming Strategy for Files and Directories
      • CMS
      • Open Source License
      • What Chart Library Should We Use Across Island.is?
      • What Feature Flag Service/application Should We Use at Island.is?
      • Logging, Monitoring and APM Platform
      • ADR Template
    • Log Management Policy
  • Products
    • Island.is Authentication Service
      • Terminology
      • Integration Options
      • Authentication Flows
      • Authorising API Endpoints
      • Session Lifecycle
      • Scopes and Tokens
      • Delegations
      • Configuration
      • Tools and Examples
      • Environments
      • Test IAS with Postman
    • Notifications / Hnipp
      • New Notification Setup Guide
      • Notifications service workflow overview
      • Email notifications
    • Pósthólfið
      • Security Checklist
      • Introduction
      • Skjalatilkynning API
      • Skjalaveita API
      • Sequence Diagram
      • Interfaces
    • Straumurinn (X-Road)
      • Architecture Guidelines for Service Providers and Consumers
      • Setting up an X-Road Security Server
        • Network Configuration
      • X-Road - Uppfærsla á öryggisþjónum
      • Straumurinn - Notkun og umsýsla
      • X-Road Central - current version
  • Development
    • Getting Started
    • Generating a New Project
    • Definition of done
    • Devops
      • Continuous Delivery
      • Database
      • Dockerizing
      • Environment Setup
      • Logging
      • Metrics
      • NextJS Custom Server
      • Observability
      • Operations Base Principles
      • Security
      • Service Configuration
      • Support
    • AWS Secrets
    • Feature Flags
    • Documentation Contributions
    • Defining Monorepo Boundaries With Tags
    • OpenAPI
    • Code Generation
    • Workspace Settings (Deprecated)
    • External Contributions
  • REFERENCE
    • Problems
      • 400 Validation Failed
      • 400 Attempt Failed
      • 403 Bad Subject
      • 400 500 Template API Error
    • Glossary
  • Misc
    • Guide: Adding a Payment Step to an Application
    • Guide: Enable Organisations to Make Requests to an Application
    • README Template
Powered by GitBook
On this page
  • Context and Problem Statement
  • Decision Drivers
  • Considered Options
  • Decision Outcome
  • Pros and Cons of the Options
  • Bazel
  • Nx
  • Lerna
  • Links

Was this helpful?

  1. Technical overview
  2. Architectural Decision Records

Use NX

PreviousUse Markdown Architectural Decision RecordsNextContinuous Integration

Last updated 2 years ago

Was this helpful?

  • Status: accepted

  • Deciders: devs

  • Date: 03.05.2020

Context and Problem Statement

We want a monorepo tool to help us to scale development up for multiple projects and teams. It should not be too much in the way, but help us manage code, dependencies and CI/CD.

Decision Drivers

  • Low complexity and overhead in development.

  • Fit for our stack.

  • Optimize CI/CD with dependency graphs and/or caching.

  • Flexible.

Considered Options

Decision Outcome

Chosen option: "Nx", because:

  • It's specially designed around our stack (TypeScript, React, Node.JS, NPM, ESLint, Prettier, Cypress, Jest, NextJS).

  • It's relatively easy to learn with focused documentation.

  • It has schematics to generate apps, libraries and components that includes all of our tools.

  • It is opinionated, which gives us a good base to start developing faster. Many things can still be configured or extended.

Pros and Cons of the Options

  • Good, because it's created and maintained by Google

  • Good, because it supports multiple programming languages and platforms.

  • Bad, because it's difficult to learn, with a custom BUILD files.

  • Bad, because JS support is hacky.

  • Good, because it has built in support for our stack.

  • Good, because it's been around for a while, originating in the Angular world.

  • Good, because it's designed with best practices for large scale web applications.

  • Good, because it supports elaborate code generation.

  • Good, because it helps optimise CI/CD for large projects.

  • Bad, because it's fairly opinionated.

  • Bad, because it's an open source project maintained by an agency.

  • Good, because it integrates with NPM and Yarn.

  • Good, because it's used by a lot of open source projects.

  • Bad, because it's primarily designed for managing and publishing open source projects, not building and deploying large scale applications.

Links

Bazel
Nx
Lerna
Bazel
Nx
Lerna
Why you should switch from Lerna to Nx