Q & A SESSION 2ND OF MARCH

Q: Are you creating framework from scratch?
A: No. Most of the current framework code base are public PHP packages. Such as: symfony/http-foundation, symfony/console. And quite a few more will be added during the development. However, the code of core itself — interfaces, application class, etc. are written by us from scratch.

Q: The final result will be core + plug-and-play packages?
A: Yes, that is our goal. Most of the functionality will be written as separate packages that can be added or removed anytime. Such modularity requires underlying core that “glues” it all together to be developed beforehand. We are working on that now.

Q: What database engine will you use?
A: We decided to go with ArangoDB.

Q: Will ArangoDB be around after one year?
A: We believe it will. It’s solid product. And it becomes more and more popular lately.

Q: What will be minimal requirements for framework?
A: At this moment it’s too early to tell, but we plan it to be PHP 7 — considering the fact that framework will reach usable state in around a year. In regards to database — it’s not yet known. Current stable ArangoDB version is 2.8.4.

Q: What did you not like about Magento that you are building new platform?
A: We do not plan to compete with Magento. Instead, our framework (not platform) will be designed to be easily customised to any unique requirements. Of course, the framework will provide core eCommerce functionality, that can be used right away, however, that is not our primary intention. Ease of customisation is. What we plan to avoid learning from Magento is — performance issues, code complexity, EAV model.

Q: What technologies do you plan to use on front-end?
A: SASS, Vue.js, no templating engine, keep it simple and lightweight. That’s what we can say at the moment. It is yet a long journey ahead of us before we get to work on front-end, so for now it’s just a plan, vision.