Likelihood to Recommend Laravel is ideally suited for fluent PHP developers who want a framework that can be used to both rapidly prototype web applications as well as support scalable, enterprise-level solutions. I think where it is less ideal is where the client has an expectation of using a certain CMS, or of having a certain experience on the admin side that would perhaps be better suited to a full CMS such as Drupal or WordPress. Additionally, for developers who don't want to write PHP code, Laravel may not be the best solution.
Read full review Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.
Read full review Pros Many libraries available which simplify integration of SaaS APIs within your application (eg, MailChimp, Mandrill, Stripe, Authorize.net) Pre-packaged tools to facilitate common tasks when building applications (eg, User Authentication and Authorization, Background Jobs, Queues, etc) Support for a broad set of technologies out of the box (eg, PostgreSQL, MySQL/MariaDB, MemcacheD, BeanstalkD, Redis, etc) Read full review Speed of development - time to delivery from zero to MVP was excellent Ease of use - the authoring experience is very easy to build and train PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on. Read full review Cons Significant learning curve. You cannot be an expert in a week. It takes many experimentations to properly understand the underlying concept. We ourselves learned it by using it on the job. Too much to soak in. Laravel is in everything. Any part of backend development you wish to do, Laravel has a way to do that. It is great, but also overwhelming at the same time. Vendor lock in. Once you are in Laravel, it would not be easy to switch to something else. Laracasts (their online video tutorials) are paid :( I understand the logic behind it, but I secretly wish it would be free. The eloquent ORM is not my recommendation. Let's say you want to write a join, and based on the result you wish to create two objects. If you use Laravel to do automatic joins for you, Laravel internally actually makes two calls to database and creates your two object rather than making one join call and figuring out the results. This makes your queries slow. For this reason, I use everything except eloquent from Laravel. I rather write my own native queries and control the creation of objects then rely on Laravel to do it. But I am sure with time Laravel will make fewer calls to DB. Read full review The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces. The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this. Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes. Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them. Read full review Likelihood to Renew We have invested a lot of time and energy into tailoring a solution that works for the company.
We think the new features in v6.2 will help us get to the next level
We also don't have the resources to rebuild a website platform from scratch even if we wanted to
Read full review Usability We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.
Read full review Performance I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
Read full review Support Rating You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
Read full review Alternatives Considered Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you if you have problems. Using Laravel, integration became easy with third-party libraries, but it was costly too.
Read full review I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.
Read full review Return on Investment Laravel allows us to rapidly prototype and build complete, scalable applications internally, which saves us time and allows us to have internal tools that fit out precise needs. We use Symfony for a similar purpose, but Laravel is an even higher-level framework that we find saves us substantially more time when building many types of web applications. Laravel solves many of the underlying concerns of building a large application (such as authentication, authorization, secure input handling) in the right ways. It saves us from handling those low-level concerns ourselves, potentially in a way that could take a lot of time or sets us up for issues in the future. It's tough to assign an ROI to this, but I'm sure it has prevented issues and saved time, which both have an impact on our financial situation. Read full review Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse The software is affordable with no compromises on capabilities and therefore it is gives us value for money. The templates makes the whole process easy Read full review ScreenShots