Geek Answers Handbook

What should we replace with DCOM?

We currently have several C ++ / MFC applications that communicate via DCOM. Now we will update the applications, and also want to replace DCOM with something more modern, which is easier to work with. But we do not know that. What do you think,

Edit

Sharing data is not something that may be of interest to others. This is only status information between different parts of the program running on different computers.

+8
c ++ com mfc dcom
source share
4 answers

There are many C ++ message libraries, from the old ACE to the new ones, for example, Google Protocol Buffers or Facebook (now Apache) Thrift or Cisco Etch .

I am currently well versed in ZeroMq , which can give you more than what you are used to.

+3
source share

DCOM is nothing more than a sugar coating over a riot system.

Any proper messaging system will do and allow you to actually determine where to exchange messages (which may be important for locating the point of failure / bottleneck pending).

There are two typical ways to do this, currently:

  • A clean messaging system, for example, using Google Protocols as an exchange format
  • Web service (full web service in JSON or REST API)
+2
source share

I do a lot of C ++ and Java applications using REST, and I'm pretty satisfied. REST is easily distinguished from CORBA and SOAP complexity and is flexible. I had a small part of the learning curve that was used to model things like CRUD, but now it seems even more intuitive.

Now for the C ++ side, I do not use a specific REST library, but only cURL and the XML parser (in my case CPPDOM), because C ++ applications are only clients, and servers are Java (using the Restlet environment). If you need it, there is another question in SO that recommends:

Can anyone recommend a good RESTful C / C ++ environment

I would also mention that my decision to use XML was arbitrary, and I'm seriously considering replacing it with JSON. Unless you have a specific need for XML, JSON is simpler and more lightweight. And the beauty of REST is that you can even support both along with other views if you want.

+1
source share

It depends on many factors. It can simply be replaced by .NET removal . In addition, if you intend to provide services for other components in a more standard way, Web services would be a good choice.

-one
source share

More articles:


All Articles