spectrum VS Nest

For a good reference repository, you should check out Spectrum’s GitHub repo. It’s organized well, uses good practices, and given that it is the entire Spectrum product, can provide a lot of system design and architecture insight.

You have now started on your first React Native app in Expo. This is the same tool which is used for creating apps like Facebook, Instagram, Coinbase, shopify, Tesla, Uber Eats and many more. You can read more on Expo here: https://docs.expo.dev/ or check out an open source app here: https://github.com/withspectrum/spectrum and checkout an enterprise boilerplate here: https://github.com/infinitered/ignite

GraphCDN passes subscriptions through to your origin, so they keep working just as they did before! I personally used GraphQL subscriptions with relative success at Spectrum and I'm very excited about live queries nowadays.

We were using Slate at Spectrum[0] back in 2017/2018, eventually switched to DraftJS due to cross-browser issues but that was honestly equally frustrating to use and support across many browsers.

In hindsight, we should've just had a GitHub-style markdown editor: https://mxstbr.com/thoughts/tech-choice-regrets-at-spectrum

It sounds like the situation has improved since then! I'll definitely try Tiptap if I ever need to build another RTE.

[0]: https://github.com/withspectrum/spectrum

Checkout spectrum

I was lucky enough that I somehow stumbled upon withspectrum/spectrum repo and found out that there actually are great applications running on the internet, under load and are dutifully maintained while being open-source! Spectrum has been back then one of the most eye-opening experiences for me as a junior developer. Although I didn't actually ever got to build a system like that, it taught me a great deal on how such app operates and how can various libraries be used.

Special thanks to the Spectrum Project (Here) for laying the foundations to Bulletproof Express. Also, many thanks to Node.js Best Practices (Here) and Bulletproof React (Here) for providing guidance on how Enterprise-Level Software should be written.

During last few years i managed to stumble upon a few repositories with large apps that have been a great learning source and an inspiration (such as https://github.com/withspectrum/spectrum) but these are few and far apart.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/