I'm finally working on my first microservices project of my career, and so far most design decisions have been aimed at centralization (monorepo, central GraphQL API).
I'm starting to believe microservices sounds good in theory but has absolutely no business being implemented in its purest form.
Also the Make command to build the local Docker environment can take up to 15 minutes to run on a M1 Macbook Pro. And because the environment uses an AWS token that expires every day, the command needs to be ran every day you may be working on the project. This is such an incomprehensible waste to me, have I already reached the end of my career in software development?
@hypolite I remember reading last year that Amazon was moving away from microservices. They make sense for distributed systems, but the micro part is widely open to interpretation.
If you have something that makes sense to spit up like that, do it, if not, of you understand it, just think of what is actually a good use case so you can speak about it without feeling like it's some mysterious paradigm.
@Netux I'm not in the position to make this kind of decision at the moment, but I still have to live with other people's for the foreseeable future. Including a young late-20s who knows more tool/framework names than I ever used myself for the past 15 years and uses ChatGPT to flesh out design solutions. The disconnect is total, and yet I will have to adapt to their world. Thankfully my boss is pretty patient about it, but I'm still afraid at some point I just won't be cutting it.
Add comment