<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Oracle Lite Part 3 &#8211; Our Concise Survival Kit</title>
	<atom:link href="http://technology.amis.nl/2006/05/11/oracle-lite-part-3-our-concise-survival-kit/feed/" rel="self" type="application/rss+xml" />
	<link>http://technology.amis.nl/2006/05/11/oracle-lite-part-3-our-concise-survival-kit/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=oracle-lite-part-3-our-concise-survival-kit</link>
	<description></description>
	<lastBuildDate>Fri, 12 Apr 2013 10:04:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: rekounas</title>
		<link>http://technology.amis.nl/2006/05/11/oracle-lite-part-3-our-concise-survival-kit/#comment-3238</link>
		<dc:creator>rekounas</dc:creator>
		<pubDate>Fri, 12 May 2006 03:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=1188#comment-3238</guid>
		<description><![CDATA[This is a good read.

I will be deploying a similar setup in a few months.  I have experience deploying large mobile server solutions before (1000 users, Oracle lite client databases ranging from 40 MB to 1 GB).  We kept that solution all on one server.  After a lot of painful performance tuning but in the end we were able to deploy something the client was extremely pleased with.  In fact, the Oracle Lite Solution had an average of 20-30 trouble tickets per months, versus 200-300 trouble tickets from the previous replication application.

Our new solution will have 3000 users all over the world and the application will be completely globalized utilizing Struts and Webtogo.]]></description>
		<content:encoded><![CDATA[<p>This is a good read.</p>
<p>I will be deploying a similar setup in a few months.  I have experience deploying large mobile server solutions before (1000 users, Oracle lite client databases ranging from 40 MB to 1 GB).  We kept that solution all on one server.  After a lot of painful performance tuning but in the end we were able to deploy something the client was extremely pleased with.  In fact, the Oracle Lite Solution had an average of 20-30 trouble tickets per months, versus 200-300 trouble tickets from the previous replication application.</p>
<p>Our new solution will have 3000 users all over the world and the application will be completely globalized utilizing Struts and Webtogo.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
