<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Singleton for access to very large instances</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Thu, 23 May 2013 20:28:55 -0400</pubDate>


    <item>

        <title>Re: Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[May be you can try the memory mapped usage of dataobjects for the data retrieved from database]]></description>
        

        <pubDate>Wed, 02 Apr 2008 07:00:40 -0400</pubDate>

        

        <jf:creationDate>Wed, 02 Apr 2008 07:00:40 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 02 Apr 2008 07:00:40 -0400</jf:modificationDate>
        <jf:date>Apr 2, 2008</jf:date>
        <jf:author>vivek singh</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[If the database is very large, it would be doubtfull to cache the whole. Even if it can cache now, the system would also grow continuosly. I would prefer to database optimization usage and partial caching....]]></description>
        

        <pubDate>Thu, 27 Mar 2008 03:21:02 -0400</pubDate>

        

        <jf:creationDate>Thu, 27 Mar 2008 03:21:02 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 27 Mar 2008 03:21:02 -0400</jf:modificationDate>
        <jf:date>Mar 27, 2008</jf:date>
        <jf:author>danny oentung</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[I agree with :...]]></description>
        

        <pubDate>Wed, 26 Mar 2008 12:16:41 -0400</pubDate>

        

        <jf:creationDate>Wed, 26 Mar 2008 12:16:41 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 26 Mar 2008 12:16:41 -0400</jf:modificationDate>
        <jf:date>Mar 26, 2008</jf:date>
        <jf:author>MrBigMAN</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[1. Implement caching as a singleton object...]]></description>
        

        <pubDate>Mon, 24 Mar 2008 04:33:35 -0400</pubDate>

        

        <jf:creationDate>Mon, 24 Mar 2008 04:33:35 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 24 Mar 2008 04:33:35 -0400</jf:modificationDate>
        <jf:date>Mar 24, 2008</jf:date>
        <jf:author>James David</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[The beans will be stateless. The problem is how do I hold reference to the cached objects in the stateless beans. I understand that you can keep non-conversational information in private variables but it is not guaranteed that the data is not lost.]]></description>
        

        <pubDate>Sun, 23 Mar 2008 17:15:57 -0400</pubDate>

        

        <jf:creationDate>Sun, 23 Mar 2008 17:15:57 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 23 Mar 2008 17:15:57 -0400</jf:modificationDate>
        <jf:date>Mar 23, 2008</jf:date>
        <jf:author>Andrei Vasilateanu</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[You need to make a cache of the data because very likely underlying there are many different syn and asyn data sources. But I won't implement the cache in objects, if that is your case, due to performance....]]></description>
        

        <pubDate>Sun, 23 Mar 2008 12:37:35 -0400</pubDate>

        

        <jf:creationDate>Sun, 23 Mar 2008 12:37:35 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 23 Mar 2008 12:37:35 -0400</jf:modificationDate>
        <jf:date>Mar 23, 2008</jf:date>
        <jf:author>Johnson Chen</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Premature optimizations could be an evil</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[To me this sounds like a classic premature optimization.:). Databases are fairly stable these days (ofcourse they need tuning as well)....]]></description>
        

        <pubDate>Sat, 22 Mar 2008 11:41:52 -0400</pubDate>

        

        <jf:creationDate>Sat, 22 Mar 2008 11:41:52 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 22 Mar 2008 11:41:52 -0400</jf:modificationDate>
        <jf:date>Mar 22, 2008</jf:date>
        <jf:author>Rajesh Balamohan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Singleton for access to very large instances</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48798</link>

        

        
            <description><![CDATA[I have the following design issue. I am developing an electronic health record application. I need to maintain large amount of information for each patient and there will be lots of patients (health issues, investigation results, basically anything a...]]></description>
        

        <pubDate>Sat, 22 Mar 2008 06:08:01 -0400</pubDate>

        

        <jf:creationDate>Sat, 22 Mar 2008 06:08:01 -0400</jf:creationDate>
        <jf:modificationDate>Sat, 22 Mar 2008 06:08:01 -0400</jf:modificationDate>
        <jf:date>Mar 22, 2008</jf:date>
        <jf:author>Andrei Vasilateanu</jf:author>
        <jf:replyCount>7</jf:replyCount>
    </item>



</channel>
</rss>

