[dancer-users] Ajax session handling
john at stoffel.org
Tue Nov 3 15:04:16 GMT 2015
>>>>> "Warren" == Warren Young <wyml at etr-usa.com> writes:
Warren> On Oct 31, 2015, at 3:48 AM, WK <wanradt at gmail.com> wrote:
>> 2015-10-31 0:56 GMT+02:00 Warren Young <wyml at etr-usa.com>:
>>>> Session::Simple ...
>>>> is not meant for production.
>>> That’s only true if “production” means a cluster of computers, or if you need sessions to survive a restart of the Dancer app.
>> Docs says, it is meant for testing purposes only.
Warren> That’s because in today’s cloud everything, shard everything,
Warren> no-SQL, multi-core, scale until Google buys us world, people
Warren> are starting to forget that there are still a great many
Warren> real-world tasks that run just fine on a single computer, and
Warren> have no reasonable prospect of needing a second CPU core, much
Warren> less a second computer.
Warren> Just for one public example, the Dancer Advent calendar.
Warren> Someone recently said it typically gets less than 2000 visits
Warren> monthly. That’s about one visitor every *20 minutes* on
Warren> average. You could probably run the site from a Raspberry Pi,
Warren> single-threaded, and never even know the difference from how
Warren> it’s run now.
This is exaclty where my usecase is for Dancer, small, simple sites.
Would I like to work on the big stuff? Sure, but not as a side
And as much as Warren and I have semi-clashed on this list, I think
we're both in violent agreement here. *grin*
So having Dancer do both big stuff, and small stuff, well is a good
goal. For me, the next cliff is the leap to Starman deployments.
It's yet another layer to learn and control for a deployment.
More information about the dancer-users