Sellvana versus Magento

Every once in a while, efforts are initiated to push Magento off its throne. Not often are they acknowledged or find serious following other than an initial burst. With an out of the blue funding of $5M, Sellvana might be different.

What is Sellvana?

Ecommerce enthousiasts found quite a surprise when abruptly news outlets started reporting on the brand new Sellvana ecommerce platform. Due to $5M in funding by unknown investors, Sellvana immediately jumps to attention as a platform intended to compete with eBay’s Magento.

Aiding to that assumption is co-founder Boris Gurvic, former lead technical architect of Magento and founder of the Magento-oriented Unirgy development and consultancy shop.

Sellvana promises to bring enjoyment back to ecommerce by thinking about both developers and merchants. The platform is built with PHP and features the in-house developed Fulleron framework (formerly known as Buckyball). The project will be released under the OSL 3 later this year, but for now, those interested will have to apply for a developer preview.

Surprisingly refreshing (and fast)

Powered by Bootstrap 3, Sellvana has a clean and responsive front- and back-end by default. Whereas the Magento default interface feels like nothing more than a demo which you should replace with something proper as soon as possible, the Sellvana default theme looks perfectly appropriate on its own.

Often with new ecommerce platforms which aim to battle Magento its market share (i.e Sylius or fwdCommerce), a lot is done right, but either development is getting up to speed or basic functionality found in Magento, is still missing. Not with Sellvana. Obviously, feature-wise it isn’t close to a 1:1 ratio, but right now, you could perfectly fine start a wesbshop with it.

For developers, Sellvana its keywords are true modularity, enhanced performance, ease of development and a fast learning curve. We will get back to the technical details a bit later. Performance-wise, we are already impressed. On the same machine, Sellvana pages load a lot faster than Magento theirs and functionality-wise the average Joe won’t notice a difference.

Merchants get a bit of the same, but also “superior SEO features” and other powerful new features. On top of that, they get a innuitive back-office even their minors can operate without thorough training or features hidden deep in sub-menus.

Architecture

With Boris as a co-founder, it’s no surprise that a lot of the architecture of Sellvana seems to be inspired by Magento. Is this some copy-paste job gone wrong? Quite the contrary: Sellvana feels like a fresh take on Magento its architecture.

Twig on the front-end

To the frustration of a lot of front-end developers, Magento does not offer a templating engine. Sadly, Magento 2 will not either. Sellvana ships with Twig as a proven templating engine. No more hard-coded PHP nested within HTML files. Instead, you get expressive syntax specifically intended to output data and manage views, even view inheritance and section-hooks – without the verbosity of XML!

Fulleron

With Fulleron instead of Zend, Sellvana arguably has a lot cleaner and less abstract foundation. It is a separate entity and can already be used stand-alone from Sellvana: Fulleron on Github. Major difference: wheras Magento rolls its own ORM (Varien backed by the Zend database component), Fulleron is a lot leaner by simply using Paris, an Active Record implementation of Idiorm.

A highly modular event-driven approach is the road Sellvana rides. Magento does too, but Sellvana steps it up a notch: basically everthing but the very absolute core is decoupled into modules and can be turned off – we tried! Note that instead of heavy XML files, expresiveness is key again with YAML as Sellvana its description-model. Looking at the inner workings of some default modules, we immediately believe there is ease of development and a fast learning curve: all of the code is very expressive.

EAV simplified

An entity-attribute-value approach is extremely effective in online ecommerce due to the nature of the differences in goods being sold. However, it adds a massive abstraction-layer between the chair with its custom properties in the shopping cart, and the representation of it in the database. In Magento’s case, the translation is slow and the code used can get immensly complex; astract-abstract-abstract class anyone?

Sellvana does away with all this complexity. We didn’t extensively research the EAV-implementation used, but by the looks of it, products have sane defaults (description and SKU straight in the products table) but can be extended by a variety of fields belonging to a fieldset. Instead of a dozen of relational tables, products self-host serialized EAV-data for quick access.

Any points for Magento?

Theoretically, Magento is simply better because it is longer in the wild than that Sellvana is in development. The developer preview really impresses us, but we can’t deny it isn’t a proven platform yet. There will probably be hiccups in true production not encounterd before, just like there will be clearly things it will immediately beat Magento at.

Though Sellvana really throws some good punches at Magento, we think that, in its complete form, Magento 2 would have been able to subvert most of them. However, Magento 2 is not complete. To be fair, neither is Sellvana but looking at the code right now, we see no sign of namespaces, PSR-compatibility or Composer dependency-loading whilst Magento 2 already got those or is working hard to provide them.

Conclusion

Inevitably something which is being used for years has a lot broader and more diverse adoption than something which only exists as a developer preview. Sellvana probably hasn’t reached its final form yet, but even in today’s form it easily outperforms Magento on some aspects.

A lot of Sellvana its success will depend on whether it is able to build on the current spike of approval and attention before Magento will properly transition to the long awaited version two. Years ago, nobody foresaw that MySpace would lose to Facebook in the time span it did. A few years ahead, it might feel like over tomorrow Sellvana replaced Magento. Or, Sellvana becomes a novelty platform in the shadow of Magento 2

We can’t look ahead in time, but no matter what will happen, Sellvana is really a platform to keep an eye on. Not because it got $5M in funding for reasons yet unknown, but because it effectively battles very specific pain-points developers and merchants have with Magento.

Disclaimer: This is a write-up on the closed developer preview of Sellvana its alpha version. It is not ready for demonstration. Technical details might change over time.

  • Alex

    You have the links wrong – the links are .com not .org

  • nevvermind

    I’ll talk about innovation and the framework behind Sellvana. I’m angry.nnFulleron or whatever it might be called could indeed provide the needed push towards a.. erm.. greater PHP ecosystem, because, as they say – “Competition is good, it drives innovation and prevents stagnation”. You could write a lot about this almost defensive answer that says so much that it ends up with no message. nnI didn’t even knew about this Fulleron thing until Sellvana. I’ve seen this before: a new ecosystem *forces* upon its inhabitants ITS means of survival, yelling that THEY’re the best means. Of course they are: it’s YOUR ecosystem, isn’t it? That’s not quality. That’s… nothing. It says nothing about the quality. Nothing. And, yeah, vendor lock-ins are not exactly wombs of imagination and evolution. And don’t even get me started with that yaml shit.nnI’m revolted, because, you know, I REALLY wanted a good framework, man! And not to learn from it – that would be a plus, but to have a solid foundation for a future ecosystem. I really hoped that! And what’s more solid to a community than the convention? You know what I mean – the “through Magento I learned ZF” kind of convention, the synergistic convention, the community-friendly convention, the “new-organism-old-parts” convention, the “built on the shoulders of giants” humble, slow but strong evolution. nnSpare me the innovation part. How many innovations are justifiable to a community of thousands? There they are, PHPers trying to standardize the autoloaders, the code style etc., and here it is – a 4-contributors framework, with a “in your face” attitude, with the eternal “we’re different, thus innovative” rhetoric.nnEvery new framework – shitty or not – hides behind the innovation thing, as if innovation means *more frameworks*. It means BETTER frameworks. Actually, scratch that – what does “innovation” even means in this context? You’d have to have a very pretty image of yourself if you think you can be TRULY innovative in PHP. Sorry, yaml routing or yaml-whatever don’t count.nnAnyway, I don’t see how multiple classes in a single script file is a good start. Call me a reactionary.nnBut it’s my duty to be fair. Innovations are not taken lightly: they stir the cozy and reassuring daily habit. I’ll try Sellvana. See what it has to teach me.