Daniel Opitz

[Daniel Opitz @dopitz]

@fullstacklover 3NF

[Daniel Opitz @dopitz]

@asaio87 ?

[Tony Ma @t1o6n3y]

🚨 Security vulnerabilities reported in a SINGLE day:

PHP — 2 CVEs
Node.js — 10 CVEs
NGINX — 5 CVEs
Go — 1 CVE
GitLab — 12 CVEs
eMudhra — CA certificate compromise

[Daniel Opitz @dopitz]

@Aditya_181105 In Vault

[Daniel Opitz @dopitz]

@IamAroke 3NF

[Daniel Opitz @dopitz]

@davidfowl Is this Perl?

[Daniel Opitz @dopitz]

A well-crafted AGENTS.md file is a game changer.

[Daniel Opitz @dopitz]

@SumitM_X There should be no JWT for a public API.

[Daniel Opitz @dopitz]

@OskarStark Another underrated advantage of PHP (and dynamic/interpreted languages in general) over classically compiled ones like Java or C#: Coding agents have access to the source files of the packages.

[Daniel Opitz @dopitz]

@brendt_gd Nice, but in this example it's not clear what method would be called if you pass a string.

[Daniel Opitz @dopitz]

@Dave_DotNet No, because this suffix adds noise without much benefit. It's also redundant because the return type already signals "this is async".

[Ed Andersen @edandersen]

JWT tokens vs cookies

[Daniel Opitz @dopitz]

@ECMAScript4 Germany isn't bad at software, it's bad at turning software into global products.
SAP dominates ERP, Nextcloud leads in self-hosting.
What's missing: speed, risk "appetite", product focus. Engineering culture ≠ startup culture.

[Daniel Opitz @dopitz]

@AntonMartyniuk HATEOAS never worked in real world scenarios. This is why we call them RESTful and not REST.

[Dr Milan Milanović @milan_milanovic]

𝗪𝗵𝘆 𝗱𝗼𝗲𝘀 𝗚𝗼𝗼𝗴𝗹𝗲 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱 𝗠𝗼𝗱𝘂𝗹𝗮𝗿 𝗠𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀?

Over the last decade, we have witnessed a significant trend of utilizing microservices across various industries. We were building systems for a few hundred or thousand users and wanted to know how to make a system for millions of users. This was over-engineering and needed to be corrected.

Why was it wrong? Because the development lasted a long time, we created incredibly complex systems, which are hard to maintain. This is especially true for startups that must go fast and stay simple.

A recent paper by authors from Google found that most of their developers split binaries for one of the following reasons: to improve performance, enhance fault tolerance, and establish abstraction boundaries, allowing for flexible rollouts.

Yet, splitting applications into microservices has its challenges:

🔹 𝗜𝘁 𝗵𝘂𝗿𝘁𝘀 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲. The overhead of serializing data and sending it across the network is becoming an increasingly significant bottleneck.

🔹 𝗜𝘁 𝗵𝘂𝗿𝘁𝘀 𝗰𝗼𝗿𝗿𝗲𝗰𝘁𝗻𝗲𝘀𝘀. It is incredibly challenging to reason about the interactions between every deployed version of every microservice.

🔹 𝗜𝘁 𝘁𝗮𝗸𝗲𝘀 𝘄𝗼𝗿𝗸 𝘁𝗼 𝗺𝗮𝗻𝗮𝗴𝗲. Rather than having a single binary to build, test, and deploy, developers must manage n different binaries, each on its release schedule.

🔹 𝗜𝘁 𝗳𝗿𝗲𝗲𝘇𝗲𝘀 𝗔𝗣𝗜𝘀. Once a microservice establishes an API, it becomes easier to change by breaking the other services that consume the API.

So, they proposed the following approach:

𝟭. 𝗪𝗿𝗶𝘁𝗲 𝗺𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝗶𝗰 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 that are modularized into logically distinct components. A component is a long-lived agent, similar to an actor.

𝟮. 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗮 𝗿𝘂𝗻𝘁𝗶𝗺𝗲 𝘁𝗼 𝗱𝘆𝗻𝗮𝗺𝗶𝗰𝗮𝗹𝗹𝘆 and automatically assign logistical components to physical processes based on execution characteristics. Therefore, if both components are in the same OS process, they are referred to as regular method calls. However, if they are co-located, calls are executed as remote procedure calls (RPCs) over the network. Runtime decides whether these modules should be collocated or moved to different machines (and scaled, etc.).

𝟯. 𝗗𝗲𝗽𝗹𝗼𝘆 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝘁𝗼𝗺𝗶𝗰𝗮𝗹𝗹𝘆, preventing different versions of an application from interacting.

This approach consists of two main parts: a programming model with abstraction that allows developers to write modularized applications and a runtime for building, deploying, and optimizing these applications. They claim that it reduces application latency by up to 15 times and costs by up to 9 times by simplifying application management and deployment.

If you want to check the framework that implements the approach from the paper, please visit https:// serviceweaver. dev/.

What do you think about this approach? Does it look like EJBs or CORBA?

[Ángel Guzmán Maeso @shakaran87]

Almost 2500 people online at #PHPVerse 2025

30 Years of PHP celebration!

https://t.co/pSJ6W9NpSy

[Daniel Opitz @dopitz]

@mjovanovictech The anemic domain model is how it should be.

[trish @TrisH0x2A]

Unpopular opinion: Side projects will teach you more than certifications ever will.

Build something. Break it. Repeat.

[Hussein Nasser @hnasr]

https://t.co/h9BYOySwBH

[Daniel Opitz @dopitz]

@DavidKPiano Maybe, because this is what a DI container should do. 😜