What is Boomla?
To give you an idea:
- Boomla is a platform for building websites.
- Goal: simplify creating websites and web applications.
- Boomla does what a CMS (Content Management System) does,
but in a very different way.
- Boomla was designed to support high concurrency without the complexity.
You don’t need to worry about locking issues, as requests work on filesystem
forks. We serialize concurrent requests for you, handle merging or replay
fully async under the hood, but it provides a sync programming environment, so you
get both speed and simplicity.
- Boomla is fully transactional. A request either makes all changes
successfully, or none at all. Including filesystem changes.
- Boomla is designed to be a standalone software. You don’t need a stack, like
LAMP + WordPress. Also, you can just sign up and use it.
- Boomla comes with built-in version control: enjoy undo; access branches on
subdomains like branch.example.com. (No, it is not built on Git, but it’s similar.)
- Boomla is object oriented. Objects and classes are files and file types in Boomla.
- Everything is a file.
- Simplicity. Both for end-users and developers.
- Encapsulation is a huge problem on the Web. CSS files and assets directories are a mess.
- You have to deal with lots of legacy. 3 users (Linux, DB, CMS), 3 kinds of access control,
2 totally different data stores (DB, FS). Not in Boomla.
- The LAMP stack is a stack, not a platform. Because your website has external
dependencies, version controlling it is extremely complex (eg. PHP extensions are not
part of your website’s codebase).