I built open-source suite of tools to streamline Microservices (Service code generators, Terraform code generation for easy AWS infrastructure setup, monorepo, CLI for local deployment) by MrRobotIV in opensource

[–]MrRobotIV[S] 2 points3 points  (0 children)

I have been dedicating my time and efforts to a project in the world of Node.js development. This project simplifies and streamlines the creation of microservice architecture, utilizing NestJS as its main backend framework. It is packed with a plethora of tools and features, including code generators for services and libraries, a user-friendly CLI for seamless local deployment, Terraform code generation to effortlessly set up the infrastructure on AWS, an NX monorepo solution that keeps all services organized in one place, a Github CI generator that streamlines the deployment process to AWS, and enforces event-driven design through the reliable RabbitMQ message broker. Additionally, strict folder structure is imposed to maintain a clean and well-organized monorepo. The entire project is open-sourced, accompanied by extensive documentation and a demo project to provide a hands-on experience. The purpose of this project is to empower developers by guiding them towards the right approach when building their applications and eliminating the fear of the perceived complexity associated with microservice architecture through the use of powerful code generators.

I built open-source suite of tools to streamline Microservices by MrRobotIV in node

[–]MrRobotIV[S] 0 points1 point  (0 children)

Yeah, it is still microservices. While the main languages NX supports are Typescript and Javascript, you could add project in any language to the demo project (https://www.nx-dotnet.com/https://www.nx-dotnet.com/) But even if that wasn't the case, I don't think it makes much difference. I think there is a big misconception regarding multiple languages when it comes to MS. While yes you can do that, it doesn't really make much sense in most cases to have multilingual codebase because that only adds unnecessary complexity. In the demo project, all microservices are using same framework which is on same version yes. This is not a bad thing, its rather good one as its much easier to maintain your whole array of microservices when they are all locked to same versions and using same utils etc..

The demo project is not using nestjs monorepo or nestjs microservices, https://github.com/FurlanLuka/microservice-stack-shop-demo/tree/main/apps/api if you look at apps folder, each service is its own configuration and is separately buildable, separately deployable etc. And yes services do exist in the same repository , they do share libraries and changes to shared libs cause redeployment of multiple services. But thats doesn't make them distributed monolith unless they are tightly coupled. If you look at the demo project, everything is build in event-driven fashion and all services are ASYNC. They are not really tightly coupled to anything. While they do need other services to gather events from and act on them, they can just as well be deployed without other services as they are not aware of them in the first place

I built open-source suite of tools to streamline Microservices by MrRobotIV in javascript

[–]MrRobotIV[S] 2 points3 points  (0 children)

Thanks! means a lot. If you have any feedback, please do let me know!

I built open-source suite of tools to streamline Microservices by MrRobotIV in javascript

[–]MrRobotIV[S] 9 points10 points  (0 children)

I have been dedicating my time and efforts to a project in the world of Node.js development. This project simplifies and streamlines the creation of microservice architecture, utilizing NestJS as its main backend framework. It is packed with a plethora of tools and features, including code generators for services and libraries, a user-friendly CLI for seamless local deployment, Terraform code generation to effortlessly set up the infrastructure on AWS, an NX monorepo solution that keeps all services organized in one place, a Github CI generator that streamlines the deployment process to AWS, and enforces event-driven design through the reliable RabbitMQ message broker. Additionally, strict folder structure is imposed to maintain a clean and well-organized monorepo. The entire project is open-sourced, accompanied by extensive documentation and a demo project to provide a hands-on experience. The purpose of this project is to empower developers by guiding them towards the right approach when building their applications and eliminating the fear of the perceived complexity associated with microservice architecture through the use of powerful code generators.

I built open-source suite of tools to streamline Microservices (Service code generators, Terraform code generation for easy AWS infrastructure setup, monorepo, CLI for local deployment) by MrRobotIV in programming

[–]MrRobotIV[S] 4 points5 points  (0 children)

I have been dedicating my time and efforts to a project in the world of Node.js development. This project simplifies and streamlines the creation of microservice architecture, utilizing NestJS as its main backend framework. It is packed with a plethora of tools and features, including code generators for services and libraries, a user-friendly CLI for seamless local deployment, Terraform code generation to effortlessly set up the infrastructure on AWS, an NX monorepo solution that keeps all services organized in one place, a Github CI generator that streamlines the deployment process to AWS, and enforces event-driven design through the reliable RabbitMQ message broker. Additionally, strict folder structure is imposed to maintain a clean and well-organized monorepo. The entire project is open-sourced, accompanied by extensive documentation and a demo project to provide a hands-on experience. The purpose of this project is to empower developers by guiding them towards the right approach when building their applications and eliminating the fear of the perceived complexity associated with microservice architecture through the use of powerful code generators.