[safaci2000]

This blog articles feels too black or white.

There's a middle ground between microservices and de-coupling. The UI can be written in JS/TS with a backend written in a more scalable faster language. It doesn't need to be all or nothing? Even if you stick to Ruby pulling some things apart due to separate concern/responsibilities is not a bad approach. Aka if you have workers/cleanup operations they don't need to live in the same code as your REST/MVC code base.

Also, it would be nice if their CI/CD could be defined in multiple .yml instead of one giant file that I seem to end up in most projects.

[jmholla]

> Also, it would be nice if their CI/CD could be defined in multiple .yml instead of one giant file that I seem to end up in most projects.

It can. You can use `include` to include templates and job definitions from other files. Also, with child pipelines (i.e. trigger jobs), you can run a pipeline defined in a separate YAML file.

[safaci2000]

sure, I've touched on include a bit and removes some of the repetitive code.

I would rather have something like:

release.yml documentation.yml security-scan.yml

I know you can define all these in a common repo and then have a few lines to include them but it's not exactly the same IMO.

Not to mention that now I need to pull another repo to see what is going on and why the task no longer works.