Paying for goods with Bitcoin is becoming more and more popular. If you run, maintain or develop an e-commerce website, ICO project, exchange, or trading system, you may be interested in a quick way of integrating with the Bitcoin blockchain.
This article will show one of many ways of installing a Bitcoin mining software and integrating a PHP application with it. I will present how to generate an address for your users and check if the transactions are confirmed.
During my journey with the cryptocurrency, I realized this is a common problem to find a highly qualified programmer who used to work with the cryptocurrency network. This is like finding a big panda in China – they are super rare. So, finally I was called a big panda and because I like to have some big panda friends, I decided to share the knowledge and my experience.
I will create a set of articles about the blockchain, the idea and general view, cryptocurrency – the Bitcoin, the Ethereum (including smart contracts), EOS (new fancy cryptocurrency that may be a trendsetter next year) and all troubles and problems that we faced.
From my personal experience, it came that the blockchain idea is both – technical and intricate. Coding without a strong knowledge about the background and idea of the blockchain brings to a lot of confusion and misunderstanding. Let’s start with the idea.
Queuing in the background – getting started with RabbitMQ message broker
In PHP business logic is usually put right in action’s method or just behind it. Hence, every little piece of delaying and long-running code will be processed with a request. The problem is almost undetectable if a user sends an e-mail but with more complex actions it may take a little bit longer than preferred.
A couple of months ago I have started my adventure with CakePhp and as every Symfony’s developer I thought that any other framework except Symfony is a piece of crap. Day by day and step by step I began to realize that’s not so bad as it seemed to be in the beginning. Well, the second version of CakePhp still has a lot old-fashioned patterns, singletons or lack of tests, but I can live with that. I saw a lot of better or worse frameworks in my life. However, one module remains a bitter aftertaste – the router.
Event Driven Design is really popular topic for about two years and I don’t suprised this trend. You can really fast decouple parts of code without any influence on any other – you can send emails, saving logs or data to database without additional mess in your core class. Continue reading