Perl Entwickler Vortrag zum Thema Shopsoftware in Perl, Herausforderungen und Ausblick.

1. Shopsoftware in PERL
for 25 years.
A success story for the community
experience & outlook 🚀

2. How
everything
began…
• 1997 Foundation on the rooftop of a house
• 1998 Websites built with Frontpage
• 1999 Used cars website for a car dealership
• 2001 complete conversion to mySQL

3. Larger
Customers
• 2005 construction of Conrad Electronic emergency system
• Very often live, because SAP had problems
• 35 server incl. loadbalancing
• Mod_Perl
• 200.000 Euro turnover per hour
• 2006 construction of babymarkt.de
• 2009 winners of the Shop Usability Award
• 2010 Babymarkt was sold to Tengelmann Ventures
• At that time approx 7000 orders per day on 27 servers

4. Make
or
buy?
• Journey towards Shopware
• Outsource core development
• Found incompatible Modules
• Trouble with customers
• „Role backwards“  CosmoShop rulez!

5. Conequent
specialization
• Consequent B2B orientation
• Occupy niches (Merch, Procurement, SAP)
• Sales are appreciated more
• Legally grateful / no warning
• no voice commerce, no headless, etc..
• no SEO / user frequency required
B2B Orientation

6. Development
Challanges
• Convert monolithic system
• Transformation to cloudsystem
• Update capability is expected

7. Measures
• Template administration, web-based

8. Code
&
new
employees
• Optimize the onboarding of new employees
• Expand wiki style documentation
• Training modules
• Simplify code base

9. updatability
• Update capability of the system is essential
• Customizable core
• Methods extensible & replaceable
• Templates can be overwritten
• Can extend core
• Provide templates
• Register routes

10. CosmoPlugins
• Introduction of CosmoPlugins
• User, installation & core plugins
• Libraries that customize & extend the core
• Cross-customer reusable
• Can be customized
• Updateability of CosmoPlugins guaranteed
• Unified & faster installation
• Soon: consolidation in app store

11. Problem
Definition
• Core can only be extended by plugins
• Extension more complex than average
• Specific extension requires a plugin
• High implementation effort

12. Outlook
• Module-based framework
• Core only one module within the framework
• Customized functions possible without plugin
• Fallback to routes of the current system
• Core can be extended according to customer requirements
• Continues to be updateable

13. THX
For your attention!
Time for a change?
www.cosmoshop.de/jobs/
We
are
the
ones
with
the
funny
T-shirts