January 24, 2012
by Patrick McGarry @scuttlemonkey
One of the driving principles behind the sale of Perforce has always been to make it extremely simple and up front. We all know how frustrating it is to check out a product online and when it comes time to evaluate it seriously, you are met with a contact form and zero pricing information. So Perforce created a simple pricing scheme without all the games.Posted In:
January 20, 2012
by Bryan PendletonPosted In:
January 18, 2012
by Mark Warren
(Doesn't everyone need a "Saa..." abbreviation to be cool these days?!)
I've just been reading an interesting article about the role of software in medical devices. A lot of sensible comments are made by the various contributors and a couple stood out for me:Posted In:
January 16, 2012
by Rusty Jackson
I often hear, and even throw the two things together in the same sentence myself, but they are two different things, and how you approach each one is important.
HA, in most users minds, means a machine that can immediately take over in case of a problem with the main machine with little down time, and no loss of data. Most often, they expect this to even be an automated process. For this task, I have always, and still do, recommend using clustering software and storing your metadata and versioned files on shared storage. The metadata should be on a fast/local SAN and the versioned files can be on either SAN or NAS for this setup. Since the data is on shared storage that can be moved between the two nodes of a cluster, no replication is required, and fail over and fail back can easily be handled by the clustering software.
DR, on the other hand, is something intended to take over in the event of a (surprise) disaster at the main site. Things like Recover Point Objective (RPO) and Recover Time Objective (RTO) come into the discussion and replication is definitely involved. There is an expected amount of data loss (RPO) expressed not in amount of data, but in an amount of time. For example, you might say that you expect to lose no more than one hour of transactions on your Perforce server if you fail over to the DR site. The RTO is how long you expect the it to take to get the server up and running at the DR site. That can be a longer period of time than the RPO since other factors are often involved like changing DNS entries, etc.Posted In:
January 13, 2012
by James Creasy
"Use the right tool for the job." my father would say, as he hammered a screwdriver into a rusted set of brake drums.
Of course, if you don't have a chisel, you make do with what you have at hand. But when a tool better suited for the task at hand comes along, you are smart to start using it.
January 11, 2012
by Duncan Barbee
P4VS is the soon to be released plug-in for Microsoft's Visual Studio. It will provide a more powerful seamless integration for developers in Visual Studio. It allows developers to perform most of their Perforce tasks from within the IDE, such as checking out files to creating and submitting changelists.Posted In: