You can write your glue nano-service in c/c++ if you want, it’s just that: glue. It doesn’t matter as long as you don’t need to change the original services which also can be written in whatever you want. Ruby, Python, JS just work out of the box with aws lambda and you don’t really have to maintain them or any sort of build infra so it allows for very little maintenance or upkeep cost. You don’t really test these glue lambdas either.
Things won’t be simpler just because you cut everything up in tiny tiny pieces (I mean it will be easier because it solves some surface level problem right now, pushing the real problem down the road), it creates a complexity of its own.
Because I clearly said that you don’t cut up things into tiny pieces. It was both in the first paragraph in my post and the last one. I said you use tiny functions to glue together larger systems. So yeah you clearly didn’t read what I wrote.
I literally didn’t mention micro services at all. So once again it’s very clear you didn’t read what I wrote. And no, that’s not what micro services are. Smdh.
Who cares if you mentioned it? Don’t you know what microservices are?
You seem to just want to be “right”, so sure continue with your new “nano services” if that’s your thing, sheesh. Just watch out for those pico-services.
This looks like hell.
I’m a C/C++ developer though.
Ya feel good about yourself, slugger? /s
Yeah, I kind of am. Just found a 33% time job so that I can gradually leave software engineering 😁
You can write your glue nano-service in c/c++ if you want, it’s just that: glue. It doesn’t matter as long as you don’t need to change the original services which also can be written in whatever you want. Ruby, Python, JS just work out of the box with aws lambda and you don’t really have to maintain them or any sort of build infra so it allows for very little maintenance or upkeep cost. You don’t really test these glue lambdas either.
Things won’t be simpler just because you cut everything up in tiny tiny pieces (I mean it will be easier because it solves some surface level problem right now, pushing the real problem down the road), it creates a complexity of its own.
You didn’t read what I wrote at all.
It’s easy to say I didn’t read your message, which I obviously did (why write lies like that?), just because you don’t understand my point.
Because I clearly said that you don’t cut up things into tiny pieces. It was both in the first paragraph in my post and the last one. I said you use tiny functions to glue together larger systems. So yeah you clearly didn’t read what I wrote.
Micro services is already cutting stuff up in small pieces lol.
The opposite us monolithic software.
I literally didn’t mention micro services at all. So once again it’s very clear you didn’t read what I wrote. And no, that’s not what micro services are. Smdh.
Who cares if you mentioned it? Don’t you know what microservices are?
You seem to just want to be “right”, so sure continue with your new “nano services” if that’s your thing, sheesh. Just watch out for those pico-services.