Comments on: Oracle-BEA Strategy http://www.column2.com/2008/10/oracle-bea-strategy/ BPM, Enterprise 2.0 and technology trends in business. Mon, 15 Mar 2010 10:08:40 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Sandy Kemsley http://www.column2.com/2008/10/oracle-bea-strategy/comment-page-1/#comment-9719 Sandy Kemsley Mon, 27 Oct 2008 20:03:53 +0000 http://www.column2.com/2008/10/oracle-bea-strategy/#comment-9719 Interesting that the analysts are taking a "wait and see" attitude about Oracle -- they don't want to be naysayers about the big O, but they're really not sure how all this confusion is going to go down in the marketplace. I completely agree with you, Oracle has made this much to complex. Interesting that the analysts are taking a “wait and see” attitude about Oracle — they don’t want to be naysayers about the big O, but they’re really not sure how all this confusion is going to go down in the marketplace. I completely agree with you, Oracle has made this much to complex.

]]> By: Alex Neihaus http://www.column2.com/2008/10/oracle-bea-strategy/comment-page-1/#comment-9567 Alex Neihaus Thu, 16 Oct 2008 00:35:21 +0000 http://www.column2.com/2008/10/oracle-bea-strategy/#comment-9567 Hi, Sandy. For us, it's pretty simple: there's no reason -- none -- that creating services-based applications has to be this hard. I'll bet Oracle customers get a headache just thinking about what this combination or that permutation could be. If Oracle is taking a beating, it's not due to the slow pace of enterprise development. Instead, it's because no customer -- even their current ones -- should be expected to engineer Oracle piece parts together into coherent products by themselves in their own shop. And that's precisely what Oracle is forcing them to do, because everyone knows this fundamental truth about commercial software development: what was designed as a separate product remains a separate product, even when you smash it together with some glue or UI. Hi, Sandy.

For us, it’s pretty simple: there’s no reason — none — that creating services-based applications has to be this hard. I’ll bet Oracle customers get a headache just thinking about what this combination or that permutation could be.

If Oracle is taking a beating, it’s not due to the slow pace of enterprise development. Instead, it’s because no customer — even their current ones — should be expected to engineer Oracle piece parts together into coherent products by themselves in their own shop. And that’s precisely what Oracle is forcing them to do, because everyone knows this fundamental truth about commercial software development: what was designed as a separate product remains a separate product, even when you smash it together with some glue or UI.

]]>