Follow 451 CAOS Links live @caostheory on Twitter and
Identi.ca“Tracking the open source news wires, so you don’t have
to.”

*451 CAOS Links will return on August 25*

Digesting the VMware-SpringSource deal
In the wake of VMware’s acquisition of SpringSource the WSJ
examined Peter
Fenton’s open source investment portfolio and what he looks for
in an open source vendor. Meanwhile Matt Asay noted that VMware’s
purchase of SpringSource is the first big acquisition of a
company based on an Apache license, while Charles Babcock
reported …

EC2 is nifty, but it doesn’t appear suitable for all needs, and
that’s what this post is about.

For instance, a machine can just “disappear”. You can set things
up to automatically start a new instance to replace it, but if
you just committed a transaction it’s likely to be lost: MySQL
replication is asynchronous, EBS which is slower if you commit
your transactions on it, or EBS snapshots which are only
periodic (you’d have to add foo on the application end). This
adds complexity, and thus the question arises whether EC2 is the
best solution for systems where this is a concern.

When pondering this, there are two important factors to consider:
a database server needs cores, RAM and reasonably low-latency
disk access, and application servers should be near their
database server. This means you shouldn’t split app and db
servers to different hosting/cloud providers.

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.