Full Stack Support
Our full stack support includes all components you use on the site – nginx, mysql, php, Magento / WordPress / standard framework, redis, mongodb, memcached, etc.
We also support any architecture – from single server to autoscaling infrastructure.
In combination of our devops support we help with documentation, automation and reconfiguration of architecture as the application grows.
luroConnect Advanced Stack
We support all versions of Magento any sized store / architecture.
Magento is powerful but notorious for its infrastructure maintenance overhead. We take this headache away from you. We support all components of your stack – from nginx, mysql and php to sphinx or SOLR search engine, redis caching and even autoscaling. All our services cater to all components.
php configuration for performance requires knowing how many CPUs are available to run php. For example, if you have a single 8 CPU (4 cores with hyperthreading) and you are running the entire stack including mysql, redis, nginx we would use a max of 6 for simultaneous php processes.
Great performance from mysql is available from Percona. We use features such as one file per table for write speed, direct write to disk for data safety and optimal cache configuration for speeding up page response.
If you bulk upload products, you would need a way to bulk upload images. There is no reliable way of giving a write only access to just the upload folder. Our stack supports uploading to a folder whose content is them magically moved to the final destination.
Magento creates right sized images in the product/cache folder. Our stack automagically optimizes the images at the system level, without a plugin. Original image files are not changed. The compression is lossy for jpeg files with a controllable quality allowing for a right balance between image quality and size. The image creation is CDN compatible.
css and js files are minfied by a “offline” process. Minified files are sometimes erroneous. This is due to the minifier being strict about syntax. For example a css file with a “//” comment. With our minifier system, you can exclude files.
Blacklist IP addresses that are either suspicious or spamy. Magento reports the IP addresses that perform actions like creating a new registration. Alternatively log files can be analyzed to determine the list. luroConnect / Insight reports top IP addresses hitting the site. Once you know what IPs you do not want, add to our blacklist. Our nginx configuration will do the rest.
A basic DOS protection is to restrict number of hits from a single IP address. Our configuration file defaults to enabling this protection. Hits from the same IP address are limited to the rate specified. Hits faster than the rate are first queued and then rejected. luroConnect / Insight reports these for review.
Your own IP addresses can be whitelisted to bypass this check.
Over 60% of traffic is generated from BOTs or programmatic access to the web server. Many of them are crawlers. While some such as google are essential, however, most of them are not. BOTs use resources and cause a caches to be misled with what is important, both leading to slowdown of web sites. Actively managing BOT access is essential.
When you upgrade your code you need to put the site in maintenance. Magento’s default functionality is a switch – either everyone sees a maintenance page or every one sees the live site. Our private mode, implemented as a nginx configuration, has whiltelist IPs that get to see the live site while other IPs see the maintenance page.
We support any standard php frameworks – such as cakephp, laravel 4.x and 5.x.
We discuss your architecture and make a bespoke support plan.
While Magento’s search has improved, external search can give features not possible with mysql search. Magento Commerce / Enterprise supports SOLR and ElasticSearch out of the box. However, requires configuration and management.
(Beta) A WAF based on open source ModSecurity is a standard part of our stack. Having a WAF as close to the server hosting the website is the best configuration. It avoids dual https hops for each request. With our WAF built into nginx, you have a superior edge protection.
Magento defaults to file system for caches and sessions. We use redis based in-memory cache. With separate redis processes for Magento cache, Full Page Cache and Sessions, Magento sites can easily server TTFB of under 1 second.
Magento 2 supports Varnish out-of-the-box for Full Page Cache. However, there are 2 problems – some 3rd party plugins do not support Varnish. Also, given that varnish does not support https, it is difficult to configure. Our Magento 2 stack supports varnish as well as redis based Full Page Cache, allowing maximum flexibility in speed and configuration.