- Full page caching (proactive, materialization) built in to both Magento 2.0 Community and Magneto 2.0 Enterprise - This means that instead of your Web server having to do a tremendous amount of slow database queries to render a page, this system builds out all of your pages in a static file system, so that page load times are 1-2 seconds (vs. 5-10 for non-cached pages). This is a huge deal.
- Streamlined Checkout Process - Nearly 80% of current Magento ecommerce sites have modified their checkout process to better streamline the process. With the Magento 2.0 checkout, guest checkout is assumed, and if you’re an existing customer, you can still log out without having to remember your password. Pesky things like having to choose credit card type have been removed. (It’s easy for a computer to figure out your credit card type based on the first digit: 3 = Amex, 4 = Visa, 5 = MasterCard, etc.)
- A clean, modern code base - Magento 2.0 is a fresh start. Merchants who want to go with Magento 2.0 will know that legacy extensions or old, bad code will be removed. There’s no easy way to leave non-optimized code in place for Magento 2.0 sites.
- Better performance / reduced table locking - With larger scale Magento Enterprise and Magento Community sites, we’ve seen performance issues with table locking when too many people are trying to place orders on a site. For example, if you have 120 people trying to check out per minute, and you have queries that take 1 second to execute (and need to lock a table to write), then your system will crash. For example, before an order is saved in Magento 1.9, the system saves key information to a Sales Grid Flat Table, so that a Magento admin user is able to see the new order in the Magento admin. But in order to do this, it has to lock the table, and this can back up processes to where people have 45 second or more page load times. We’ve gotten around this specific issue with crazy levels of caching and very esoteric MySQL table optimization. But Magento 2.0 Community / Magento 2.0 Enterprise promises to have reduced this issue considerably.
- Database is no longer a single point of failure - Magento 2.0 Enterprise allows you to separate your databases. You can have one MySQL database that is responsible for serving all of the content pages, product and category pages. You can scale this out with caching, and allow tens of thousands of people to hit these pages. But once someone adds something to the cart, you can separate this out to have the checkout process use a completely separate database. This allows you to have much, much better performance, and make sure that people who are trying to checkout won’t be slowed down by people just trying to browse (but not purchase). For bigger sites that do 5,000+ orders a day, this will make a big difference.
