Because developers always think they can do it better themselves.
APIs are cool. And building an eCommerce framework based on APIs sounded really cool. This started as an experiment trying out the Moltin service and turned into a project to try out shiny and new PHP stuff. A proof of concept to show the world eCommerce doesn't have to be monolithic.
We're not trying to replace existing eCommerce systems but augment them in a way that offers you, the developer, the ability to use the libraries you want, the Javascript framework you want and anything else you want to try out.
Swapping out any part of the application for another solution should be easy. The idea of KickAss is to offer API based middleware between various services.
We want to have you choose the libraries and techstack you work with. The goal is to make all code undependant of each other by using Dependency Injection.
Classes are ordered by their domain. Anything concerning products (except bridge classes) can be find in src/Product.
Wondering where you can find a class? Just think of what domain it belongs to.
Why did we choose the libraries we did
we needed a basic and easy to use library for routing. SlimPHP is battle tested, fast to implement and offers just the right features we needed. Which was mainly routing
Every application needs configuration. DotEnv offers an easy way to read .env files which are, for now, good enough
for credentials, basic feature flags and other small settings
Because we love to convert anything to everything and nothing beats Symfony serializer
You want to add business logic? Of course you do! Just DONT EDIT THE CORE! Put that stuff in the app directly using
Aspects brought to you by Go! AOP. Check out
PSR/Cache offers a standard easy to use caching library with various adapters of which we by default use filesystem. There might be better caching systems but we were looking for something basic and easy. You can always implement your own of course.