CHRIS: Beyond that, there's also dynamic content caching that we can do, such that when someone makes a request to the site and they're asking for a list of bids based on this filter, et cetera, et cetera, we can then cache that request. And if anyone else within a certain time period makes the same request, we don't have to hit the infrastructure to ask for the calculations and the CPU and the RAM and the hard drives we use. We have that in a noSQL cache.
You can just think of that like, “you just heard something from someone, and you remember it, and you don't need to go look it up.” It's the same thing for the application. The application has this ability to have a short-term memory, if you will, and this is really what the cache is. So we can configure this and optimize it and precede that cache so that when users are on the site, it's extremely performant and it also reduces your overhead for your infrastructure.
So these two are tuned, as you grow your eAuction business, hand in hand. It can be somewhat expensive over time, to continue the performance tune the application side of things beyond a certain threshold, there's a law of diminishing returns there. So you want to essentially increase the infrastructure, where it takes a lot of effort to increase the performance of the application. And then once you get to a certain level of traffic and performance or need, then further optimize the application and just keep tweaking as you scale your business.
So you really want to look for a partner who can help you with this so that you can get an immediate value for your eAuction platform, that doesn't require a lot of setup and sophisticated configuration, that just works and is performant. But it needs to be architected and designed and have a plan to be able to scale it up over the next three to five years.
So that's what we look to do, Ron, whenever we're working with clients. And I know that this is always a challenge for clients, right? Because as they scale their business, we don't want them to be painted into a corner from a performance perspective.
RON: Well, and we never know what scaling means [to them. Does it] mean they divest and sell off pieces of the business as they get wildly successful? When I was at tech company and we started being successful, it meant acquisitions. We acquired nine different companies over the course of just a few years, and we grew.
When we left Novell, there were about 12 of us, and we grew it to almost 2000 employees. So I mean, what is scaling? Does scaling mean three guys in a garage start up an online auction site and it goes from 10 auctions a day to 10,000 auctions and it's still three guys. It's a tiny group, right? It's a small group of people, but the site itself is wildly successful. or it could be going worldwide with a global auction platform. You mentioned the CDN and caching the images, right? Does that mean we go globally and the infrastructure scales with B2B auctions?