Disclaimer• I am jonasbn -
like almost everywhere• Long time Perl and web developer• Open Source/CPAN contributor and previously freelance developer in logicLAB• Currently employed with DK Hostmaster• I have no afﬁliation with ActiveState
(My) Developer Needs• Easy access
to platform, runtimes and frameworks• The least possible gap between development, test and production• Minimal differences between deployed code and the code in the editor• reproducibility for transparency
What do we have?• Unit-tests•
Mocked objects and classes, stubs a.s.o• Local servers / emulators• Virtualization• Dedicated environments (dev/test/prod)• Code - lots of code...
Stackato• A micro-cloud • current
version 1.0.6 • out of beta, released 2012.02.29• Platform as a Service (PaaS) private and public• Supporting several languages, their frameworks and commonly-used services
operating• start, start a service•
stop, stop a service• restart, restart a service• this is about it, for what I can provide for now, I have no experience with long time operation of a Stackato deployed service• Oh there is one more thing...
Targets!• Multiple targets • development
/ test / production• Targets make sense in SCM context • trunk / branches / tags (releases)• You could just go for the micro-cloud, but you would loose some of the beneﬁts
My Current Road Map• Oracle
as a service (Perl driver DBD::Oracle and Oracle driver distribution issue)• Cryptographic components (export of PPMs, Perl packages)• Deployment of custom components• Service integration (PostgreSQL)• Full blown examples (Mojolicious over Mojolicious::Lite etc.)• mDNS and dynamic DNS (might be .local)• Central logging (syslog)
Beneﬁts• Easy and controlled access
to platform, runtimes and frameworks• The least possible gap between development, test and production and minimal differences between deployed code and the code in the editor depending on your cloud deployment• reproducibility for transparency since the amount of magic is kept at a minimum