"Don't only practice your art, but force your way into its secrets; art deserves that, for it and knowledge can raise man to the Divine." - Ludwig van Beethoven
In this chapter, we will delve deeper into Magento 2 module development. This is a big professional differential that you can create Magento 2 increasingly customized solutions. The importance of knowing the different layers and the interactions among the distinct components of Magento 2 increasingly contributes to your improvement and especially to the quality you will deliver in your projects.
In the previous chapter, you used the jCarousel library to enrich your theme project. In this chapter, you will make a direct integration with the Twitter REST API.
The following topics will be covered:
- Magento components
- Development workflow
- Developing the Sweet Tweet module
With the present advent of agile software development, we're increasingly seeing that developers who create a conducive environment for incremental improvements in their code deliver great value in the shortest possible time. To achieve this kind of maturity, it is necessary that professionals follow the evolution of technology, perform tests, and incorporate innovations that increase productivity in their projects and tools.
Studying the techniques that bring this benefit is very important so that we can achieve significant results as professionals in the technology area.
Until now, you realize that Magento 2 the solutions-development universe is wide and its architecture provides space for modular growth not only of themes, which are the main focus of the book, but also to modules and distinct languages that you want to use in your solutions.
For this organization to be possible between all the functional components, it is important that your code behaves according to the Magento 2 system architecture.
In a survey shown in the Magento developers area (http://devdocs.magento.com/guides/v2.0/ext-best-practices/bk-ext-best-practices.html), the distribution of used instances versus the quantity of extensions is as follows:
Note that the Community Edition and Enterprise Edition should work with more than ten extensions or modules simultaneously, so that the system runs in a transparent way and in accordance with the expectations of your users.
The evolution of Magento from version 1 to version 2 made these concepts even more evident once a series of standards had been adopted to aim for delivery quality and componentization of its modules, aiming to extend its functionality. How about a little more understanding of these standards?