TypeORM

TypeORM

Application and Data / Languages & Frameworks / Microframeworks (Backend)
Senior Software Developer at IT Minds·
Shared insights
at
()

At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

READ MORE
The Leading Web stack of an IT Minds Senior Developer. - DEV Community 👩‍💻👨‍💻 (dev.to)
13 upvotes·362.9K views
Senior Fullstack Developer at QUANTUSflow Software GmbH·

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

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token 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 is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript 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 especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js 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/TypeScript, 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 or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js 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 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.
READ MORE
25 upvotes·2.2M views
Needs advice
on
TypeORMTypeORMNext.jsNext.js
and
FirebaseFirebase

I am trying to figure out how to spin up effective React apps as fast as possible. I have loved my experience with using Next.js so far and have been using Next-Auth as an authentication process.

So far, I have used Django on the backend, but it looks like I can speed things up by ditching the backend and going serverless with the Next.js API routes. That means I am left with a database solution to figure out. Does anyone have experience using Firebase together with React, or alternatively using TypeORM with a PostgreSQL database?

I am valuing ease of development in this decision.

READ MORE
7 upvotes·36.7K views
Replies (1)
Software Engineer ·

React + Firebase is an awesome combination. Add Typescript and even better.

READ MORE
4 upvotes·1 comment·7.2K views
raphaelaudet
raphaelaudet
·
July 22nd 2021 at 8:11AM

Firebase will definitely be faster than typeorm. Typeorm seems pretty state of the art for js or ts stacks but I have been missing a lot of feat I got in other lang.

·
Reply
Junior Fullstack Developer ·
Needs advice
on
TypeORMTypeORMSequelizeSequelize
and
ElectronElectron

Hey! I am actually in internship and have an app to create for my structure. It will be an intern app which will allow crud dashboard actions with some data provided by the use of an API of one of the structure partner and make a correspondence to data contained in a private database. Since it's an intern app, I thought about Electron for a desktop app because I did a lot of web with Laravel and the structure goes more for the desktop app. But it will be my first occasion working with this tech.

Is Electron a good choice? Wich ORM should be more complete and adapted to this between Sequelize and TypeORM? (Database will be MySQL) Some charts will be displayed in the app. Is there a library (preferably without jQuery) that suits this stack?

Thank you !

READ MORE
5 upvotes·70.3K views
Replies (1)

Unless you're either using a local database or a backend server, you shouldn't choose either.

My recommendation would be having a NodeJS API on the backend that connects to the database and Electron connects to the API. Never give the database connection data to the end user, unless it's a planned move and it's to use on a local database.

I can recommend Sequelize because what I'm use the most on every project I need to create database connections. It supports TypeScript, and if you already have the database create you can use sequelize-auto to create the models, as easy as that.

I've only used Electron once and I liked it, but it's not a good comparison, since it doesn't offer any database access by default. I used React for the frontend part of the app, you can use whatever you want.

READ MORE
5 upvotes·2 comments·6.1K views
Dieudonné ALLOGNON
Dieudonné ALLOGNON
·
May 24th 2021 at 7:13AM

Thank you! That's what I finally decided. Your answer makes me sure that I am on the right track

·
Reply
Alexandre Desroches
Alexandre Desroches
·
July 25th 2021 at 4:41PM

If possible, avoid making an Electron App because the build process can be much more irritating and complex than making a web app. If you're able to use technologies like Firebase Firestore and a simple front-end to serve the data it will be hundred times faster than handling a full desktop app!

·
Reply