Until the mid-1970s, most systems were built using functional systems. Object-oriented systems were introduced with a flurry of promises in the early ‘80s, many of which actually proved to be true, for once.
More recently, people have been talking about object-based systems, object stores and object-based file systems. In this article, I’d like to clarify the characteristics of each type of technology. Truth in advertising—there’s a lot of overlap, so I’ll try to smooth out the bumps in the ride.
In my last blog, I covered the last ten years working with a particular Objectivity customer. In this blog, I want to go back even further, more than 25 years ago to the start of Objectivity.
Let me start by presenting a brief timeline:
The 1980s: Object technologies became popular, although even prior to that time, objects had been used in some significant projects. These technologies included languages, modeling, tools and databases.
1989: The Object Management Group (OMG) was formed to coordinate and standardize efforts among multiple organizations in different verticals, all trying to leverage the power of objects.
1996: The Unified Modeling Language (UML) was accepted by the OMG, unifying modeling methods from luminaries like Grady Booch, Ivar Jacobson and James Rumbaugh.
2005: A Task Force was set up with OMG to bring together multiple tools in the Business Process space.
2011: The Cloud Standards Customer Council was created.
So suffice it to say that objects have been around for a long time and are still here.
Some of the traditional Objy/DB Admin tools now use a new mechanism of execution known as tool tunner. You can find the change in tool name and tool options below. All tools now require the –bootFile flag with the bootFilePath. The following are a subset of the Objectivity DB Admin tools. More Administrative tools have been added to the tool runner interface which are listed in a separate table after the Tool Runner table.
Here are the list of tools using tool runner: