QUANTUSflow Software GmbH

On top of linting and prettifying, sonar cube gives you hints about vulnerabilities and code smells. So it has its value in checking semantics for you as well. The degree of this is easily configurable. It also can give you hints on how much effort fixes might take. The best advice is to try it on your code base and evaluate if the generated reports provide additional value to your team.

Our whole DevOps stack consists of the following tools:

• @{GitHub}|tool:27| (incl. @{GitHub Pages}|tool:683|/@{Markdown}|tool:1147| for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
• Respectively @{Git}|tool:1046| as revision control system
• @{SourceTree}|tool:1599| as @{Git}|tool:1046| GUI
• @{Visual Studio Code}|tool:4202| as IDE
• @{CircleCI}|tool:190| for continuous integration (automatize development process)
• @{Prettier}|tool:7035| / @{TSLint}|tool:5561| / @{ESLint}|tool:3337| as code linter
• @{SonarQube}|tool:2638| as quality gate
• @{Docker}|tool:586| as container management (incl. @{Docker Compose}|tool:3136| for multi-container application management)
• @{VirtualBox}|tool:774| for operating system simulation tests
• @{Kubernetes}|tool:1885| as cluster management for docker containers
• @{Heroku}|tool:133| for deploying in test environments
• @{nginx}|tool:1052| as web server (preferably used as facade server in production environment)
• @{SSLMate}|tool:2752| (using @{OpenSSL}|tool:3091|) for certificate management
• @{Amazon EC2}|tool:18| (incl. @{Amazon S3}|tool:25|) for deploying in stage (production-like) and production environments
• @{PostgreSQL}|tool:1028| as preferred database system
• @{Redis}|tool:1031| as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

• Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
• Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
• Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
• Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
• Scalability: All-in-one framework for distributed systems.
• Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.

Our whole Node.js backend stack consists of the following tools:

• @{Lerna}|tool:6207| as a tool for multi package and multi repository management
• @{npm}|tool:1120| as package manager
• @{NestJS}|tool:8747| as @{Node.js}|tool:1011| framework
• @{TypeScript}|tool:1612| as programming language
• @{ExpressJS}|tool:1163| as web server
• @{Swagger UI}|tool:3417| for visualizing and interacting with the API’s resources
• @{Postman}|tool:1336| as a tool for API development
• @{TypeORM}|tool:7419| as object relational mapping layer
• @{JSON Web Token}|tool:6417| for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

• Made for the web and widely in use: @{Node.js}|tool:1011| is a software platform for developing server-side network services. Well-known projects that rely on @{Node.js}|tool:1011| include the blogging software Ghost, the project management tool Trello and the operating system WebOS. @{Node.js}|tool:1011| requires the @{JavaScript}|tool:1209| runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies @{Node.js}|tool:1011| especially for the operation of a web server. Ryan Dahl, the developer of @{Node.js}|tool:1011|, released the first stable version on May 27, 2009. He developed @{Node.js}|tool:1011| out of dissatisfaction with the possibilities that @{JavaScript}|tool:1209| offered at the time. The basic functionality of @{Node.js}|tool:1011| has been mapped with @{JavaScript}|tool:1209| since the first version, which can be expanded with a large number of different modules. The current package managers (@{npm}|tool:1120| or @{Yarn}|tool:5848|) for @{Node.js}|tool:1011| know more than 1,000,000 of these modules.
• Fast server-side solutions: @{Node.js}|tool:1011| adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within @{JavaScript}|tool:1209|/@{TypeScript}|tool:1612|, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
• A language along the entire stack: Widely used frameworks such as @{React}|tool:1020| or @{AngularJS}|tool:1019| or @{Vue.js}|tool:3837|, which we prefer, are written in @{JavaScript}|tool:1209|/@{TypeScript}|tool:1612|. If @{Node.js}|tool:1011| is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
• Flexibility: @{Node.js}|tool:1011| sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

• @{Nuxt.js}|tool:7304| consisting of @{Vue CLI}|tool:9559|, @{Vue Router}|tool:6932|, @{vuex}|tool:6705|, @{Webpack}|tool:1682| and @{Sass}|tool:1171| (Bundler for @{HTML5}|tool:2538|, @{CSS 3}|tool:6727|), @{Babel}|tool:2739| (Transpiler for @{JavaScript}|tool:1209|),
• Vue Styleguidist as our style guide and pool of developed @{Vue.js}|tool:3837| components
• @{Vuetify}|tool:6163| as Material Component Framework (for fast app development)
• @{TypeScript}|tool:1612| as programming language
• @{Apollo}|tool:5508| / @{GraphQL}|tool:3820| (incl. @{GraphiQL}|tool:7879|) for data access layer (https://apollo.vuejs.org/)
• @{ESLint}|tool:3337|, @{TSLint}|tool:5561| and @{Prettier}|tool:7035| for coding style and code analyzes
• @{Jest}|tool:830| as testing framework
• @{Google Fonts}|tool:2652| and @{Font Awesome}|tool:3244| for typography and icon toolkit
• @{NativeScript-Vue}|tool:9623| for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

• Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
• Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
• Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
• Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
• Large scaling. Vue.js can help to develop pretty large reusable templates.
• Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.