Simples Assim » Progress Sonic

In the abstract, it’s easy to see how Oracle could use MySQL as a complement to its flagship product; MySQL for low end, low margin accounts where Oracle doesn’t currently compete or, tactically, to undermine SQL Server and/or DB2 in particular accounts.

As a few folks have pointed out, the Oracle sales force is going to dislike MySQL even more than the Sun sales force did, as it is a low margin product competing – at least in some sense – with a high margin staple.

I also agree that Oracle and MySQL aren’t really competitors, unlike Sonic (proprietary and outdated) and FUSE (open source and leading-edge), which is another interesting story to follow.

http://redmonk.com/sogrady/2009/10/23/oracle-mysql-and-the-eu-the-qa/

Thanks to Simon for the tip.

Prestadores de Serviço com Progress Sonic ESB

Fernando Ribeiro — Sat, 24 Oct 2009 23:42:01 +0000

Progress Sonic Customers List

Fernando Ribeiro — Thu, 24 Sep 2009 01:33:26 +0000

If you have to mix references, you probably don’t think that you have enough.

http://www.sonicsoftware.com/customers/index.ssp

Many well-known customers are missing, go figure why.

Issue in Progress Sonic Workbench 7.6.2

Fernando Ribeiro — Mon, 21 Sep 2009 03:44:12 +0000

When using the Asynchronous Event Dispatch API with a few thousand messages, I got a bunch of javax.naming.NameNotFoundException exceptions about temporary queues in MgmtBroker that Progress Sonic Workbench seems to fail to create.

No exceptions were thrown when the process ran from the JMS Test Client.

I will open a ticket ASAP.

Asynchronous Dispatching in Progress Sonic ESB 7.5+

Fernando Ribeiro — Sat, 19 Sep 2009 19:52:38 +0000

All messages placed in the Outbox by a service are sent at one time. A service can create multiple messages and address them to multiple endpoints. None of these messages are sent until the entire service (XQServiceContext ctx) method has completed.

(from the page 89 of the Developer’s Guide)

[The Asynchronous Event Dispatch API] allows message dispatching at any time after service initialization and provides direct access to the framework dispatch mechanism instead of requiring messages to be placed in the service Outbox.

(from the page 321 of the Developer’s Guide)

public void service(final XQServiceContext ctx) {
  final XQMessage msg = ...

  final XQDispatch dispatcher = ctx.getDispatcher();

  dispatcher.dispatch(msg);
}

There is a SentWithDispatch metric in 7.6 that is also of interest.