Magento Commerce Cloud: 10 New Features

The Magento has announced its Commerce Cloud offering almost about two years back in 2016. From then to till now, approximately 500 Magento Commerce consumers have signed-up to launch on Magento Cloud and 150+ stores already have gone live.

Magento has observed an unnatural adoption in its service, and now-days, about 50% of new customers are selecting Magento to develop on Magento Cloud alternatively of placing on third-party infrastructure suppliers.

Throughout all that development, Magento product and engineering teams have been listening keenly to the feedback from their customers and then working dynamically to improve it. Additionally to upraise some seriously amazing updates to the solution.

Today, we want to share 10 new Magento Commerce Cloud features the most significant changes that Magento has made recently. To be sure that you are getting advantages of these amazing updates you must upgrade to the latest ece-tools package.

Manage and Deploy Stores With New ECE-Tools Package

Magento has launched and ece-tools package to provide a candidly mature and scalable deployment tool which can scale with its consumer’s requirements. In 2018 February, Magento has removed “ecc-patches” and “Magento cloud configuration” packages and provides a path for advanced Magento version to run along with the ece-tools package

Integrating to single package across all version permits traders a simple path for upgrading their occurrence and let Magento concentrate on releasing updates more frequently with the rich standard.

Production Deployment And Configuration Workflow

When the Magento launched Cloud first time, developers had to use three complete individual repos for managing their integration, staging, and production environments. But the staging or production environments were unavailable by the Cloud UI or CLI.

This means, after the development of the integration environments, developers had to push to an individual production repo. This created friction in the deployment procedure. Additionally, many configurations and management options for staging or production environments needed manual work from the Magento Support Team.

Last year in October, Magento launched two important improvements for good developer experience.

Inaugurated staging/production git repos with the help of Cloud UI and merged the whole environment into a solitary Git tree, clarifying the code merging and deployment procedure.

Facilitated self-seek configuration, and management of staging or production environments, so that the developers can directly perform these tasks as mentioned below:

  • Add or remove the user from staging/production
  • Add or remove variable to staging/production
  • Add post_deploy phase support and cache warming
  • Manage to build or deploy hooks and PHP version through

Production Deployment: Increased Speed

While deploying to the production site, the duration of the maintenance mode on site depends on the overall size of the site and changes made during that deployment, but the biggest factor in the size of static content such as images, javascript, css, video, And even whole web pages.

In quarter 4th of the year 2017, Magento launched two alternatives “how they manage Static Content Deployment”, which lowers the maintenance window conspicuously:

  1. First, the possible way for incrementation of the speed of production deployments is to transfer the SCD to the build phase of the deployment and to enable better reducing which is the default and runs on the fly-as-opposed to keep it as a dependency on the deployment.
  2. Disable full static content deployment and whenever the page is requested, run it on demand.
  • Move SCD to on demand mode
  • Enable post_deploy hook
  • Enable cache warm up

With these improvements, customers have increased their production deployment speed significantly and Magento highly recommends all customers to provide these features a spin.

Simplified Process Management: Build/Deploy

Magento had launched Cloud, developers required to add a few project level variables through the web UI to organize the build/deploy process.

Magento initiated the .magento.env.yaml file in January 2018, which stores build/deploy process all configuration. Now the developers can configure any phase of the deployment process:

  • Global
  • Build
  • Deploy
  • Post_deploy

These changes help developers to organize the configuration and make variable changes instantly. This new configuration process is also backward compatible with the past configuration settings

Performance Boost

Magento has launched a new feature which permits Pro customers to use the capability of all three nodes available on MariaDB and Radis Pro production environments. If this feature gets enabled, all operations will write single (master) nodes, while the read operation will be balanced between 3 nodes. This feature gives a vital performance boost when enabled.

Local Development Template To Ease Cloud Deployments

When Magento launched the cloud, developers had to install and find out their local development environment on their computer. They launched a clean and lightweight Magento-Cloud template in February 2018, which ensures the local build commands will not affect the code which will ultimately be pushed to the remote (i.e. cloud) environment.

Increase Available Memory (100%)

Magento uses Amazon Web Services as a service for the Magneto Cloud as a built-in infrastructure. When Magento launched Cloud Offering, they were primarily using the “C3” family of servers for the production environment related to Pro customers.

In Q8 2018, Magento started executing the AWS M4 family of servers for new customers and started migrating all existing customers to the same M4 family of the server – there is no cost for the trader and no trader had no downtime effect.

M4 servers give extra than 100 percent increase in available memory. It will have an instant and important positive effect on performance. Over the next few months, Magento is migrating to all advanced customers to ensure that there is no service obstacle.

The second step of going into the M4 family, which starts from the end of May 2018, is the re-configuration and tuning of internal features such as REDIS cache, MYSQL buffer and query cache, and the elastic search, which provides additional performance improvements

Fastly Web Application FireWall: Enhanced Security

Magento Commerce (Cloud) depends on a shared responsibility security model. In this model, various parties have different areas of responsibility to maintain system security. This shared responsibility approach permits flexibility and the use of best-of-breed cloud technologies.

customers have the full potential to customize the Magento app as any deployment model. Additionally, managed services are provided as the part of the Magento offered. This offer has been made on top of Amazon’s industry-leading cloud services. The objective of this approach is to provide the greatest flexibility for adaptation and innovation while reducing the operational responsibilities of the trader.

As part of Magento’s security leadership, Magento has currently started the rollout of a web app firewall which is powered by Fastly. WAF avert malicious traffic from entering the site/network.

WAF Magento will provide security against OWASP Top 10 and will be rolled out to all customers who will depend on a templed rule based on test traffic on cloud sites. WAF rules will then be adjusted on the basis of per change in the security environment.

Generally, traders need to source, implement and pay for their own WAF to avoid malicious traffic. Magento is in the operation of listening/learning from last quarter and rolling it on to all customers at Q2 and Q3 as a standard part of Cloud infrastructure.

Fastly Image Optimization: 20%+ Page Speed Improvements

Magento Commerce Cloud is adding another mighty feature to all existing and new customers for free-image optimization which is powered by Fastly. Great eCommerce sites depend on high-quality images that help end users browse and buy their desired products. Nevertheless, these quality images are usually a large part of the performance slowdown sites that appear on their forehead.

With Fastly image optimization, merchants will see significant performance improvements. We have seen a rise of 20 to 30 percent increase in Google Page Speed score of sites and see a 60-90 percent reduction in image weight at no extra cost. Fastly CDN Built, FIO permits their consumers to change and serve images on the edge without affecting the original server.

Magento rolls out the IO to all existing and new customers on Q2 and Q3 as the standard feature of Magento Commerce Cloud. With more instructions on how to take advantage of image optimization, traders and partners should anticipate notification of a support ticket in June.

Keeping Up With PCI Compliance

To establish a secure website connection older than Transport Layer Security (TLS) 1.2, protocols do not meet the minimum safety standards due to security vulnerabilities. In order to ensure the safety of its store and to maintain PCI compliance, Magento Commerce Cloud only started to restrict connections to TLS 1.2 or more and is now available inbound by visitors using earlier versions of TLS and SSL Connection does not accept.

If you still find any problem or need any assistance, feel free to call on our support number +1 888 614 0555. We are here to provide you the best solution

Leave a Reply