The new beta version contains a lot of improvements and focuses on:
- Even more performance
- Developer experience
- Code cleanup
The new beta version contains a lot of improvements and focuses on:
Does an online shop with 1 billion items work on a standard cloud server? And that even with the demand for very low response times? We investigated this question during the #gigacommerce project.
The #gigacommerce setup contains 1 billion articles, which are combined into 10 million products. Each item contains attributes, images, prices and text like in any online store. The basis is a Symfony, Laravel and TYPO3 installation with the Aimeos E-Commerce extension, which access an ElasticSearch server.
All three frontends have been extensively tested to find out where the limits are. The Aimeos components showed that they scale almost infinitely, with response times of around 100 milliseconds. Interestingly, the only absolute limit in the tests was not the available hardware, but the network bandwidth, which was used up at over 600 PI/second. This makes it particularly interesting for peak load situations and TV advertising.
Content commerce, the fusion of editorial content and e-commerce, is a growing area gaining more and more importance for businesses.
We have been on the first European Content Commerce Summit in Leipzig (Germany) for two days spotting the latest trends and and held a session about Aimeos as solution for integrating content and e-commerce to interested participants.
The offered sessions had a wide range of topics, from the very interesting talk from Danny Nauth about the secrets of successful content based on the experience of neural marketing, over content along the customer journey by Kai Wermer and the importance of the right content for SEO by Markus Hoevener to tops and flops in content commerce projects by Hannes Richter from Projecter.
Roman Zenner had some bad luck with the beamer but used that problem as a smart excuse for having no presentation at all 😉
To sum up: A really cool event for everyone interested in all aspects of content and e-commerce!
Modern PHP applications consists of thousands of PHP files. Even if your own set of files is small, most of the functionality is nowadays provided by 3rd party libraries. Especially composer made it simpler than never before to integrate external libraries and full stack frameworks like Laravel or Symfony contains a lot of them. The Aimeos e-commerce components are not different in this case since this kind of code reuse is the best thing since sliced bread 🙂
The TYPO3 caching framework is a great way to speed up your site if your extension needs to perform tasks that can be cached. In the Aimeos TYPO3 extension, we use it to store content like list or detail views of the web shop to get lightning fast response times. Since version 6.2, a cache can belong to one or more cache groups in the caching framework and it enables editors to control more precisely which caches should be flushed. Unfortunately, this features isn’t well documented yet in the TYPO3 documentation but here’s the remedy!
The cool thing about the TYPO3 bootstrap_package extension is that you can set up a new site within minutes because everything is pre-configured. This also includes the RealURL setup so you already see the page titles in your URLs and the language parameter value is mapped too.
This article is for Neos 2.0 and thing migt have changed in the meantime. At least the software packages are required in newer versions.
Neos is well known for its well designed interface for editors who quickly fall in love with the system. On the other hand, it’s also infamous for being hard to set up by starters due to its high demands towards the hosting environment. Someone also compared it to walking on a slack line: It’s easy to stumble and to get frustrated.
This article focuses on creating a hosting environment suited for Neos so you will be able to finish the Neos setup and get a running instance afterwards. I’m using Ubuntu 14.04 as reference but it also applies to other Linux distributions like Fedora, only the path names might differ a bit (
After months of development we’ve felt ready to release the first stable version of our Open Source web shop bundle for the Symfony PHP framework.
The shop bundle enables software developers to integrate e-commerce functionality into their applications immediately. Pre-configured pages and a complete demo data set reduces the time to the first working shop down to a few minutes, increasing productivity. And the best thing: It integrates well with existing bundles like FOSUserBundle for user registration and management!
Our attention has been laid on creating a high-performance shop bundle that scales up to 100 000+ products on a standard Linux/Apache/MySQL/PHP stack. With additional software such as ElasticSearch, several million products per installation are possible without performance loss and in optimized server setups, we’ve seen response times down to 40ms.
As usability is one of the key success factors of online shops today, we’ve continuously tested and improved the user experience. The Aimeos “elegance” theme is the result which we are very proud of. If you are a developers who would like to create new themes, you are also able to completely rework the front-end by adding, removing or reordering all aspects only via configuration settings.
We hope you enjoy the bundle as much as we do! The new version and additional information is available at the Symfony web shop bundle page
Simplicity is key! I think nobody would oppose to this little sentence but in the TYPO3 ecosystem, many things are not very simple – at least not for new users. Even the most popular extensions need a deep knowledge of how to configure them before they can be used. And good documentation is most of time a rare thing!
So why not build an extension that works out of the box and configures itself as far as possible to give users an instant feeling of success? The
setup.txt TypoScript files of the extensions can contain almost all default settings. But things get difficult if the required configuration depends on dynamic things like page IDs. Then, all hope of simplicity is lost and users have to add the necessary settings themselves again.
Extensions are a great way to add features to the TYPO3 CMS and there are extension for virtually everything! Simply download them from the TYPO3 extension repository and install them via the Extension Manager in the TYPO3 back-end. So far so good …
Often, the remaining tasks of configuring the extension, adding new pages with the plug-ins from the extension or importing required data into the database becomes much more cumbersome. Why can’t life be not as easy as in other CMS? Just click and everything works?