I use hetzner.com . (does not affiliate, unlike the article) Cheaper than DigitalOcean. Higher processing power but lower disk speed than DO droplets. I host my personal software delivery pipeline on 4gb ram instance on hetzner. Jenkins for CI/CD and Nexus as an artifact repository. Both runs fine in same instance via docker. I'll add my personal blog to another instance in the following months.

No offense fellow Laravel developers! But Laravel is a total joke when compared to Symfony . Symfony components are getting more independed and decoupled from each other. The framework avoids magic as much as possible while promoting usage of interfaces, abstractions and types. And these things affects greatly to the code you write. It makes you to think abstract and modular, instead of procedural and concrete. Writing decoupled & modular software using Laravel is possible, however there is one caveat: You must to be already good at it. Otherwise, with the practises that Laravel promotes (too much magic, less abstraction) you will struggle to learn basics of modular and managable software.

This maybe a little of topic introduction, but for your own favor, please don't implement microservices pattern if you don't have a proper use case. Otherwise you will suffer. :) For the communication part, you can use REST APIs and sockets. Leveraging REST is rather easy. But If you don't have experience in sockets and more importantly your framework of choice doesn't have prebuilt libraries for leveraging sockets it can be problematic. Sockets are less expensive than REST APIs. And offcourse you can use messaging queues for async communication. Learning CQRS can help you a lot with microservices. Command and Query are general operations we use when developing software. Consider this task: Update status of the user with the ID 5 and send an email regarding the update. There are three operations in this task can be simplified as follows: Fetch the user with the ID 5 Update status of the user. Send an email. Where 1 is a query and 2 and 3 are commands. Queries are mostly sync where commands are async. So first item should be in sync because you are querying some service and you want to hear back from the service with the details of the user. For the first item we can create a query. Like this. class FetchUserById { protected int userId; constuctor( int userId) { this .userId = userId; } } Message bus is used to serialize the message (above) and send it to related source via your transport of choice. You can choose REST, Socket (which will be synchronous) or amqp to have async behaviour. Operation 2 and 3 can be async, so we can utilize appropriate messaging bus that uses amqp as transport.

i will delete it in a moment. thanks.

I've made a typo on a join clause of very long SQL query, ended up with sending 118 emails to wrong clients. My mistake was: ... join user on application.id = user.id Instead of: ... join user on application.user_id = user.id Big facepalm.

It reminded me question "what is a panzerschreck?" The answer was "it schrecks panzers" indeed. :) maybe following image give you an idea how does url shortener redirects to origin url.

I don't have one in my current company. However, managers who constantly checks for development progress (more than five times a day) have been my biggest distraction.

I don't get it why companies still asks same old algorithm questions. They are mostly related with algebra and don't help with understanding candidate's software design capabilities. I wouldn't hire a candidate who cracks the coding interview but writes lots of unmaintainable, conditional flooded code.

Proudly self-taught software developer. Interested in object oriented analysis and design, along with the domain driven development. My main programming language is PHP, and most favourite framework is Symfony. I'm learning JAVA, because i like strongly typed languages.

You need to get familiar with the docker concepts first. It's mandatory since you want to build a rather complicated production stack. Get familiar with Dockerfile first. Learn how to build images. Docker images are immutable, which means you build them once (via Dockerfile) and use them "as is". However, you can persist data via bind mounts and volumes. Get used to them. Learn differences. Once you familiarized with the docker images and containers concepts you can dive in to orchestration of docker images. Learn docker-compose. You can have launch configurations in docker-compose for your stacks. After all of this, you can learn kubernetes for managing containers. You can find prebuilt images for each application like php, mysql, redis, rabbitmq. I usually use prebuild images for services that aren't exposed to public IP, like mysql and redis. However, i avoid using prebuilt nginx and php images on production stack, as they expose to public IP directly and their defaults (configurations, installation paths) are open sourced. One of my laravel project's Dockerfile: FROM debian: 9.5 MAINTAINER Tuncay Uner <mail@address> ARG LOCAL_USER_ID= 1000 ARG LOCAL_GROUP_ID= 1000 # UPGRADE PACKAGES RUN apt- get update && \ apt- get -y upgrade # INSTALL PREREQUISITES RUN apt- get install -y aptitude RUN aptitude install -y sudo RUN aptitude install -y libssl-dev RUN aptitude install -y wget RUN aptitude install -y curl RUN aptitude install -y unzip RUN aptitude install -y locales RUN aptitude install -y cron RUN aptitude install -y rsyslog # PHP REPOSITORY RUN apt- get -y install apt-transport-https lsb-release ca-certificates && \ wget -O /etc/apt/trusted.gpg.d/php.gpg https: //packages.sury.org/php/apt.gpg && \ sh -c 'echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" > /etc/apt/sources.list.d/php.list' # NODEJS REPOSITORY RUN curl -sL https: //deb.nodesource.com/setup_10.x -o nodesource_setup.sh && \ sh nodesource_setup.sh && \ rm nodesource_setup.sh # UPDATE PACKAGE INDEX RUN apt- get update # INSTALL PHP RUN aptitude install -y php7 .2 -fpm RUN aptitude install -y php7 .2 -gd RUN aptitude install -y php7 .2 -zip RUN aptitude install -y php7 .2 -xml RUN aptitude install -y php7 .2 -intl RUN aptitude install -y php7 .2 -mbstring RUN aptitude install -y php7 .2 -pdo-mysql # INSTALL NODE RUN aptitude install -y nodejs # INSTALL NGINX RUN aptitude install -y nginx # CREATE USER & GROUP "user" RUN groupdel dialout && \ groupadd --gid $LOCAL_GROUP_ID --non-unique --force user && \ useradd --uid $LOCAL_USER_ID --gid $LOCAL_GROUP_ID --shell /bin/bash --create-home --non-unique user # CREATE FOLDERS RUN runuser -l user -c 'mkdir webroot' && \ runuser -l user -c 'mkdir log' # REMOVE DEFAULT SITES RUN rm /etc/nginx/sites-enabled/ default RUN rm /etc/nginx/sites-available/ default # INSTALL COMPOSER COPY ./script/install-composer.sh /root/install-composer.sh RUN sh /root/install-composer.sh # ALLOW "user" MANAGE SERVICES COPY ./config/sudoers.d_service /etc/sudoers.d/service # ENTRYPOINT COPY ./script/entrypoint.sh /home/user/entrypoint.sh And docker-compose.yml: version : '3.5' services: app: user: user container_name: project_app build: context: .docker dockerfile: Dockerfile volumes: - ./.docker/config/development/php-fpm-pool. conf: /etc/php/ 7.2 /fpm/pool.d/project.conf - ./.docker/config/development/nginx. conf: /etc/nginx/sites-available/project - ./ :/home/user/webroot :delegated working_dir: /home/user/webroot ports: - 8000 : 80 entrypoint: sh /home/user/entrypoint.sh networks: - development environment: TZ: Europe/Istanbul db: container_name: project_db image: mysql: 5.7 . 23 command: --default-authentication-plugin=mysql_native_password restart: always volumes: - project_data: /var/lib/mysql - ./.docker/config/mysql_max_allowed_packet. cnf: /etc/mysql/mysql.conf.d/mysql_max_allowed_packet.cnf - ./.docker/config/mysql_sql_mode. cnf: /etc/mysql/mysql.conf.d/mysql_sql_mode.cnf ports: - 3306 : 3306 networks: - development environment: MYSQL_ROOT_PASSWORD: root MYSQL_DATABASE: user MYSQL_USER: user MYSQL_PASSWORD: user TZ: Europe/Istanbul cache: container_name: project_cache image: redis: 4.0 . 10 volumes: - project_cache: /data entrypoint: redis-server --appendonly yes networks: - development volumes: project_data: project_cache: networks: development: name: development