Close
  • Latest News
  • Big Data and Analytics
  • Cloud
  • Networking
  • Cybersecurity
  • Applications
  • IT Management
  • Storage
  • Sponsored
  • Mobile
  • Small Business
  • Development
  • Database
  • Servers
  • Android
  • Apple
  • Innovation
  • Blogs
  • PC Hardware
  • Reviews
  • Search Engines
  • Virtualization
Read Down
Sign in
Close
Welcome!Log into your account
Forgot your password?
Read Down
Password recovery
Recover your password
Close
Search
Menu
Search
  • Latest News
  • Big Data and Analytics
  • Cloud
  • Networking
  • Cybersecurity
  • Applications
  • IT Management
  • Storage
  • Sponsored
  • Mobile
  • Small Business
  • Development
  • Database
  • Servers
  • Android
  • Apple
  • Innovation
  • Blogs
  • PC Hardware
  • Reviews
  • Search Engines
  • Virtualization
More
    Home Development
    • Development

    Persistent Objects, Persistent Issues

    By
    Peter Coffee
    -
    August 12, 2002
    Share
    Facebook
    Twitter
    Linkedin

      When I saw an eWEEK story late last month on new business continuity and disaster recovery services, it made me think about the problem of persistent objects. Let me explain that leap.

      Suppose that all of the people in your firm suddenly vanished: no damage to your offices or factories, no loss of critical data, but nothing left that had been only in peoples heads when they disappeared. “To do” items, knowledge of work in progress, thoughts about resource availability for pursuit of present and future opportunities: all gone.

      For at least a decade, weve been urging people to move beyond the Stone Age IT model of data in one place and behaviors (that is, code) in another. There are all sorts of things that are easy to do wrong when any piece of code can get at any piece of data: Unless every single piece of code knows about every single data representation, inconsistencies are easy to create and difficult to detect (let alone to repair).

      Objects are at least a Bronze Age improvement: Data carefully enclosed in the shell of the only code thats allowed to directly change it. As we move toward distributed applications with shared object populations, inconsistency remains a problem, but ideally our applications will live in a world model that represents every kind of entity that they need to manipulate or understand. The problem of managing a multi-user object-based environment is, however, far from simple.

      What happens when our goal of object representation in our IT world has to coexist with our goal of defense against the things that can go wrong in the real world? Yes, the core of an object instance may be a set of data values, and those can be backed up—but the objects shell of code may have its own state as well. What does it mean to have a backup object stored at a remote hot site?

      Im reminded of the essential problem of Star Trek transporter devices: If you cant tell me the difference between a live human being and a still-warm corpse, how do you preserve that difference while youre re-creating the body at another location?

      The transporter problem is still some years away; today, though, we can serialize objects into byte streams, putting them into a form in which they can be transmitted and stored and reconstructed at some future time. We have to be constructively paranoid about this, and again I wind up thinking of science fiction scenarios such as the problem of someone waking up my backup personality and putting it into someone elses body: Do I want the copy to know everything about me? A naïvely serialized object may contain information, such as password values, that I dont want roaming around and which I therefore need to exclude from the serialized byte stream (with a facility such as the “transient” keyword in Java).

      Its common for object-based systems to create many temporary objects, a resource and performance issue in the base case—but a real complication if we start storing objects in lots of places, since now we need to do garbage collection across those persisted copies. If were not careful, well wind up using far too much of our storage for garbage—or far too much of our bandwidth for messages asking, in effect, “Are you finished with that?”

      XML, with its inherently serial character and its ease of identifying and manipulating individual elements of a collection, is a natural candidate for persistent object storage, but making this choice opens the door to many next-level choices. Should XML files be stored in native file systems, or in a generic database management system, or in an XML-specific data management environment?

      These are fun questions to ask, since they give us an excuse to evaluate new technology, but Cameron Laird makes an important point about the need to avoid letting the choice of a tool change the definition of the problem: “You start to wonder, What does it take to maximize XML performance? The answer: You dont want to maximize your XML performance. You need to meet engineering requirements.”

      The purpose of all this effort is to build applications quickly, with high return on investment, based on choices that maximize our future ability to select from the best of the next-generation technologies. Lets persist, if youll pardon the expression, in staying focused on that goal.

      Tell me if persistent objects are old news, new news, or too-news.

      Peter Coffee
      Peter Coffee is Director of Platform Research at salesforce.com, where he serves as a liaison with the developer community to define the opportunity and clarify developers' technical requirements on the company's evolving Apex Platform. Peter previously spent 18 years with eWEEK (formerly PC Week), the national news magazine of enterprise technology practice, where he reviewed software development tools and methods and wrote regular columns on emerging technologies and professional community issues.Before he began writing full-time in 1989, Peter spent eleven years in technical and management positions at Exxon and The Aerospace Corporation, including management of the latter company's first desktop computing planning team and applied research in applications of artificial intelligence techniques. He holds an engineering degree from MIT and an MBA from Pepperdine University, he has held teaching appointments in computer science, business analytics and information systems management at Pepperdine, UCLA, and Chapman College.

      MOST POPULAR ARTICLES

      Android

      Samsung Galaxy XCover Pro: Durability for Tough...

      Chris Preimesberger - December 5, 2020 0
      Have you ever dropped your phone, winced and felt the pain as it hit the sidewalk? Either the screen splintered like a windshield being...
      Read more
      Cloud

      Why Data Security Will Face Even Harsher...

      Chris Preimesberger - December 1, 2020 0
      Who would know more about details of the hacking process than an actual former career hacker? And who wants to understand all they can...
      Read more
      Cybersecurity

      How Veritas Is Shining a Light Into...

      eWEEK EDITORS - September 25, 2020 0
      Protecting data has always been one of the most important tasks in all of IT, yet as more companies become data companies at the...
      Read more
      Big Data and Analytics

      How NVIDIA A100 Station Brings Data Center...

      Zeus Kerravala - November 18, 2020 0
      There’s little debate that graphics processor unit manufacturer NVIDIA is the de facto standard when it comes to providing silicon to power machine learning...
      Read more
      Apple

      Why iPhone 12 Pro Makes Sense for...

      Wayne Rash - November 26, 2020 0
      If you’ve been watching the Apple commercials for the past three weeks, you already know what the company thinks will happen if you buy...
      Read more

      eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site’s focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

      Facebook
      Linkedin
      RSS
      Twitter
      Youtube

      Advertisers

      Advertise with TechnologyAdvice on eWeek and our other IT-focused platforms.

      Advertise with Us

      Menu

      • About eWeek
      • Subscribe to our Newsletter
      • Latest News

      Our Brands

      • Privacy Policy
      • Terms
      • About
      • Contact
      • Advertise
      • Sitemap
      • California – Do Not Sell My Information

      Property of TechnologyAdvice.
      © 2021 TechnologyAdvice. All Rights Reserved

      Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.

      ×