<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Daniel, Petrica Andrei-Daniel</title>
    <description>The latest articles on DEV Community by Daniel, Petrica Andrei-Daniel (@danielpetrica).</description>
    <link>https://dev.to/danielpetrica</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F254697%2F8fecdc65-9ff0-436a-8390-a5cc38624155.png</url>
      <title>DEV Community: Daniel, Petrica Andrei-Daniel</title>
      <link>https://dev.to/danielpetrica</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/danielpetrica"/>
    <language>en</language>
    <item>
      <title>My new project: Coz.jp</title>
      <dc:creator>Daniel, Petrica Andrei-Daniel</dc:creator>
      <pubDate>Sun, 09 Nov 2025 06:06:40 +0000</pubDate>
      <link>https://dev.to/danielpetrica/my-new-project-cozjp-45o</link>
      <guid>https://dev.to/danielpetrica/my-new-project-cozjp-45o</guid>
      <description>&lt;p&gt;Hello, Dev Community! I'm excited to finally pull back the curtain on my latest side project: Coz.jp, a new link shortening service.&lt;/p&gt;

&lt;p&gt;While "yet another link shortener" might sound simple, the goal here was to build something fast, reliable, and deeply integrated, all while using a modern and scalable tech stack. I want to share a little bit about what it does and the architecture I chose.&lt;/p&gt;

&lt;p&gt;Why I Built It&lt;/p&gt;

&lt;p&gt;As a developer, I've always needed a link shortener that gives me full control after the link is created. That's what Coz.jp is all about: fast creation, but also the ability to go back and fix errors by editing the target URL, or deleting the link entirely. It focuses on:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Fast and Reliable URL Shortening: Speed is non-negotiable for link redirects.

Complete Link Management: Easily fix mistakes or update destinations after publishing.

Privacy-Friendly Analytics: Gain insights without compromising user security.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;The Technical Core: My Stack&lt;/p&gt;

&lt;p&gt;For a project like this, I needed a setup that was robust, easy to deploy, and scalable. I went with a modern, containerized architecture that uses some of my favorite tools:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Framework: Laravel The back-end is powered by Laravel. Its elegant syntax and robust features made developing the API endpoints and the link management dashboard incredibly efficient. Laravel's Eloquent ORM provides a secure and structured way to handle the thousands of daily redirects.

Containerization: Docker Compose Everything runs inside Docker Compose. This ensures that the local development environment is an exact mirror of the production environment, eliminating the dreaded "it works on my machine" problem and making deployment rock-solid.

Database: MySQL The reliable backbone of the application is MySQL. It handles the quick lookups required for redirects and securely stores all the user and link data.

Reverse Proxy: Traefik I used Traefik as the edge router. Traefik handles all the incoming traffic, manages HTTPS certificates automatically, and routes traffic efficiently to the correct Docker containers. This setup gives me excellent performance and a truly scalable, production-ready infrastructure.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;Ready for Your Workflow&lt;/p&gt;

&lt;p&gt;One of the key features I focused on was developer and business integration. Coz.jp offers:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Full API Integration: Ready for you to integrate into scripts or custom applications.

N8N Node: For those using low-code automation, I've built an n8n node to allow seamless integration into your automated workflows.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;You can manage your links with a simple email verification process, ensuring only you control your shortened URLs.&lt;/p&gt;

&lt;p&gt;Try It Out!&lt;/p&gt;

&lt;p&gt;I'd love for you to check it out. &lt;a&gt;You can login and Start your free trial today.&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>A Production-Ready Laravel Architecture with Traefik and FrankenPHP</title>
      <dc:creator>Daniel, Petrica Andrei-Daniel</dc:creator>
      <pubDate>Sun, 09 Nov 2025 05:49:04 +0000</pubDate>
      <link>https://dev.to/danielpetrica/a-production-ready-laravel-architecture-with-traefik-and-frankenphp-1led</link>
      <guid>https://dev.to/danielpetrica/a-production-ready-laravel-architecture-with-traefik-and-frankenphp-1led</guid>
      <description>&lt;p&gt;Laravel is a very performant framework, but a standard architecture has one big flaw derived from how PHP works: It has to rebuild the entire framework on every single request.&lt;/p&gt;

&lt;p&gt;Even with optimizations, this process still takes 40 to 60 ms on my machine with PHP 8.4. Luckily, for years, the PHP and Laravel worlds have had a solution that dramatically reduces this load time: Laravel Octane and FrankenPHP. The booting time for the Laravel framework can drop to just 4 to 6 ms per request. Incredible, isn't it?&lt;/p&gt;

&lt;p&gt;Now, if you're new to Laravel Octane or FrankenPHP, you may wonder: How is this possible?&lt;/p&gt;

&lt;p&gt;The simple answer is that the framework is kept in memory. After FrankenPHP starts, Laravel is always ready to serve requests without a full reboot. The real explanation is more complex and out of scope for this article. If you're curious, you can read the official Laravel Octane and FrankenPHP docs for a deeper dive.&lt;/p&gt;

&lt;p&gt;read the full article at: &lt;a href="https://coz.jp/IWz4E3" rel="noopener noreferrer"&gt;DanielPetrica.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>laravel</category>
      <category>webdev</category>
      <category>programming</category>
      <category>cloud</category>
    </item>
    <item>
      <title>How I Survived the Front Page of Hacker News Without Crashing My Site</title>
      <dc:creator>Daniel, Petrica Andrei-Daniel</dc:creator>
      <pubDate>Wed, 30 Apr 2025 13:00:00 +0000</pubDate>
      <link>https://dev.to/danielpetrica/how-i-survived-the-front-page-of-hacker-news-without-crashing-my-site-1h8f</link>
      <guid>https://dev.to/danielpetrica/how-i-survived-the-front-page-of-hacker-news-without-crashing-my-site-1h8f</guid>
      <description>&lt;p&gt;In this post, I share my journey of surviving a massive traffic spike when my article reached the front page of Hacker News. I discuss how I optimized my Ghost CMS setup for handling high traffic using caching strategies with Cloudflare, Docker, and Traefik. I'll also dive into practical tips on setting up caching headers and how I scaled my multi-site server infrastructure without crashing. If you’re dealing with high traffic or want to future-proof your site, this guide will help you manage big surges with ease.&lt;/p&gt;

&lt;p&gt;Read the complete article and view the graphs here: &lt;a href="https://danielpetrica.com/surviving-hacker-news-front-page/" rel="noopener noreferrer"&gt;https://danielpetrica.com/surviving-hacker-news-front-page/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>traefik</category>
      <category>cloud</category>
    </item>
  </channel>
</rss>
