Video

Great video 1) still a little confused on the volumes part of the config, but I am still learning docker on the side so maybe i havent gotten to that part yet 2) would love a very introish video to use Prometheus and grafana just enough to like take a rest api and bounce off of it 3) how do you get those awesome completions in your terminal

I completely up for a video about Prometheus and Grafana 🚀

Definitely do a video about Prometheus and Grafana

Smart move good job

just deploy the app, it best then doing all the setup

Whoa didn't know that I can use postman like this. I always manually type my input whenever I test O_O. Yes, horrible! Thanks for this dude! Will be checking on your other videos.

Boom! Here I am Seniority

Thank you for the great explanation.

Thank you very much for being open about your career path and sharing your story. wishing you all success 🌻

can you recommend me some webdev courses please ?

Thanks mate, this was helpful!

I got lost in the notation changing to TypeScript and using Axios - I'd like to implement OAuth without extra middleware processing any of the data (I get scared of MiddleWare touching sensitive data, especially if I do an update and something changed that accidentally created a vulnerability in the communication).

good content

After seeing this , Iam happy that Iam using nestjs it makes my life easy. I have to build a simple restapi using express and man this is a nightmate to write all those docs by hand

Hi, I'm really new in web development and I've got one, maybe silly, question; what is vite for here? I get we've got web server (fiber) but why do I need vite then?

yes, products service goes down and you can still have orders 😂 … and whats this “go down” issue? … what junk hardware and o/s is this running on 😂😂

hi & and i have question :) your case about GetUser... if we do not found user we simply can return an error not found. why you suggest that nil for error for this case is better ??

don't use ts-node, it doesn't support es module. instead use tsx which is lightweight and very easy to use and use helmet js,

hello, how do we access res.local.user.sesssion , since our user model does not have the session field

Love you man! I was facing issue to connect with client from my node app for an whole day, found solution to my issue in few minutes only. Thank you so much 🙇‍♂

Thanks 👍

😂😂😂😂 killed me the intro

Loving this new change

This was a real turn off. I thank the ts team for fixing it.

Hey, really liked this video. I have one question, What if we need to upload multiple files do we need to create multiple signed urls for that?

Thank you Tom...very helpful 👍

What about sign up with google?😢

I get the idea but it’s code like this that becomes a hot path really quickly. Ideally you should be aiming to touch the database as little as possible. This looks like MongoDB, but in Postgres changing this to a single query with a CTE is the way to go

I think it's useful to mention that this applies to frontend JS as well, it doesn't just apply to Node apps. Otherwise, solid advice

What is the need of promise all can't we just remove the first await??

Nice but little confusing 😂

First time hearing zsa being used with react query. Anyway to provide GitHub? I just need the code to understand.

Thank you so much for such a useful video 🔥 Cheers master!

The way to fix typescripts problem is to just use JS and to stop using TS

How do you do BFF?

I'm really greatful for such tutorial. Before knowing about all taht stuuf, I asked myself : "How cna I test my API efficiently, with the most detailed tests possible and reproductibility ?". I almost started to cre&te tests using bash & curl, and starting my server as a daemon. I knew it was not the solution, so I didn't started yet. Thanks to your video, I know the correct way now.

I remember upvoting an issue for this on typescript’s github. It’s funny that we sometimes think we’re making a mistake when in fact it’s the language.

Finally! I’ve ran into this problem before and essentially had to write my own filter method to satisfy typescript. This makes things as easy as they should be.

Nice video, it would be great if you give give little more explanation in here and there esp usage of mutate, interface, it would be good to follow along for beginners

Simple and precise !

could you make one more video with this architecture for minimum project

Great job explaining this architecture. One crucial piece that I see missing is your observability/ monitoring layer. I’ll add prometheus, grafana to collect app and infrastructure metrics. You can even spice it up a bit with jaeger for traceability. This will equip you with a feedback loop to extend your pipeline to do canary releases later on.

Tom! Why not ROR ?

Please make a minimal project using this architecture if you have the time.

Some tips based on my experience in a large project (30+ microservices, 70+ devs): DX - In cases where you have many microservices, running them all locally for development would rarely be possible. Devs would need beefy laptops to be able to run all the services, and you would also run into the issue of having different setups (eg. docker-compose) for local development and production (eg. kubernetes), which will get exponentially harder to keep in sync as you introduce more and more services and infrastructure pieces. Best approach for this (but pricy) would be to have on-demand remote environments, ideally running inside of kubernetes (or your platform of choice), in which case you eliminate most of the "works on my machine" problems, by having the devs work on the setup that's closest to production. As a bonus with this approach, you also get the benefit of being able to provide on-demand environments for QA/Compliance teams, or for any other purpose, without much effort, since it uses the same logic. Microservices - Please use kafka/rabbitmq/nats (or alternative tech) for communication between services, as opposed to having direct communication. This adds decoupling to your architecture, and will let each service run at it's own pace. This is especially useful when APIs change (like in the example from the video) so instead of having to now update all services that depend on the one that changed the api, you would only change that one, and the way it communicates with the "message bus".

Or you can just deploy LOCALLY if your target audience requires strict data privacy, has unreliable internet connectivity, or needs low-latency access to critical systems, such as in healthcare facilities or remote locations.

Shouldn't we make bff common for both mobile and web (instead of doing it twice in the next js web app and a separate mobile bff)?

very nice to see how a senior dev would approach a project architecture-wise. thank you! very useful 👏🏻👏🏻👏🏻

NextJS Layer will be using Pages or App Router? Is there any need for App Router in this architecture?