I develop modern Web applications based on Symfony 2.x (Doctrine 2.x) and symfony 1.x (Doctrine ORM 1.x) framework. Solutions, for which I use DRY and KISS rules, are created in service-oriented architecture (SOA) using design patterns.
I create high-performance solutions using variety of cacheing mechanisms and load balancing between multiple servers in system - from the level of HTTP server through the database to file systems.
Created solutions support data replication on the file system level and data base level.
Thanks to the technologies I use, created applications can run on multiple servers simultaneously. This provides the ability to easily increase computational power system in case of increased demand for it. The application architecture also provides a good use of available resources in the system.
I build applications that can be easily expanded in the future with additional features.
| PHP | |
| Frameworks | |
|---|---|
| symfony 1.x | |
| Symfony 2.x | |
| Silex microframework | |
| Zend Framework 1.x | |
| ORM's | |
| Doctrine ORM 1.x | |
| Doctrine 2.x | |
| Propel 1.x | |
| SQL databases | |
| PostgreSQL (PGPool-II) | |
| MySQL | |
| HTTP servers | |
| Apache HTTPD | |
| Cherokee | |
| nginx | |
| Apache Lucene | |
| Memcached | |
| MongoDB | |
| Varnish Cache | |
| Other technologies associated with web applications | |
| (X)HTML(5) | |
| CSS (bootstrap, yui) | |
| XML | |
| Yahoo performance rules | |
| JavaScript (AJAX, CoffeeScript, jQuery, JSON) | |
| REST (Richardson Maturity Model) | |
| Atom (RFC 4287) | |
| HTTP 1.1 (RFC 2616) | |
| Testing | |
| Selenium | |
| lime | |
| PHPUnit | |
| Version control systems | |
| git | |
| cvs, svn | |
| Other programming languages | |
| shell scripts | |
| python | |
| PyGame, PyGTK | |
| C, C++, pascal | |
| Operating systems | |
| Windows | |
| Linux | |
| Distributed file systems | |
| GlusterFS | |
| NFS | |
| Image processing | |
| GIMP, Photoshop | |
| CorelDraw | |
Below is a list of bundles that I use that are not part of the standard distribution as well as those created by me in the service-oriented architecture.
| Bundles |
|---|
| AntiMattr/GoogleBundle |
| ArmetizFacebookBundle |
| AvalancheImagineBundle |
| BeSimpleDeploymentBundle |
| BeSimpleI18nRoutingBundle |
| Desarrolla2/RSSClientBundle |
| DoctrineFixturesBundle |
| DoctrineMigrationsBundle |
| DoctrineMongoDBBundle |
| FOSCommentBundle |
| FOSFacebookBundle |
| FOSRestBundle |
| FOSTwitterBundle |
| FOSUserBundle |
| JMSAopBundle |
| JMSDebuggingBundle |
| JMSDiExtraBundle |
| JMSSecurityExtraBundle |
| JMSPaymentCoreBundle |
| JMSPaymentPaypalBundle |
| JMSSerializerBundle |
| JnsXhprofBundle |
| KnpMenuBundle |
| LiuggioExcelBundle |
| MopaBootstrapBundle |
| SMMemcacheBundle |
| SonataAdminBundle |
| SonataBlockBundle |
| SonataDoctrineMongoDBAdminBundle |
| StofDoctrineExtensionsBundle |
| My bundles |
|---|
| EventHorizonLogBundle |
| EventHorizonProfilerBundle |
| ImproCardStreamBundle - Cardstream online payment protocol support. Closed source bundle. |
| ImproPaymentBundle - universal payment subsystem. Closed source bundle. |
| ImproUserTrackBundle - user activity tracking. Closed source bundle. |
When creating appilications I pay attention to the simplicity of the solutions. If any part of a code requires a comment, it probably means that it should have been written more simple.
Testing is one of the most important element of the process of creating applications - the program should be tested at every stage of the development. Application, that is ready to use, should have a set of functional tests and unit tests, which will simplify further development of the program and will help to check the corectness of it's work.
public function getAvailability()
{
return "-ENOFREETIME";
}
I work for EXPCommerce, IMPRO and Solsken Pty Ltd