Goodbye Microservices: From 100s of problem children to 1 superstar

Re:Goodbye Microservices: From 100s of problem children to 1... by maxxxxx on Tuesday July 10, 2018 @08:41PM (#17503500)

"From an architectural perspective, there is absolutely no difference between a micro service and a library. The only real difference is in the dispatch mechanism."

I always tell people if you can't write and maintain a library then don't do microservices.

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by scruffyherder on Tuesday July 10, 2018 @10:22PM (#17503967)

Yes the kids have just rediscovered the move from COM to DCOM.

It's so silly that we are wasting so much time rebuilding existing things, poorly.

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by User23 on Tuesday July 10, 2018 @11:34PM (#17504288)

COM wasn't a picnic to work with back when it was the new thing. The toolchain sucked. I'll never write another line of MIDL in my life.

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by maxxxxx on Tuesday July 10, 2018 @11:54PM (#17504367)

Agreed. Although with tools like Visual Basic it was quite nice to use. Now, DCOM was another story. Pretty much everybody I knew who used it started to become suicidal after a while...

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by voltagex_ on Wednesday July 11, 2018 @12:05AM (#17504408)

I still maintain a (third party) app that requires DCOM.

[ Parent | on HN ]

Re:Goodbye Microservices: From 100s of problem children to 1... by pjmlp on Wednesday July 11, 2018 @01:21AM (#17504620)

MDIL has been rejuvenated for C++/WinRT, the new C++17 based projection for UWP.

[ Parent | on HN ]