mastodon 4.7.3Problem solver, software architect, also working as a Data Witcher ⚔️, hunting and killing 🧌 and 🪳in data processing pipelines! Creator of https://flow-php.com
I migrated entire Flow #PHP into Mago Linter / Formatter / Analyzer.
What before was taking more than a minute now takes 5 seconds.
One tool replaced 3 providing insane performance boost. Since Mago is also very strict it helped me to improve Flow code quality 💪
You can find slides from my talk about data processing in php at https://speakerdeck.com/norbert_tech/data-processing-in-php
I migrated Flow #PHP to Mago - for now only linter + formatter.
Performance gain is mind blowing 🤯
I also moved away from composer scripts towards just - much better DX now!
Flow #PHP Arrow Extension is live!
flow-php/arrow-ext
It provides a parquet reader/writer which is automatically picked up by flow-php/parquet when available.
This makes php parquet even faster than python pyarrow implementation.
Flow #PHP 0.38.0 is out!
It's a technical release that doesn't bring too many new features. Recently I have been mostly focused on moving project to Mago Analyzer (formatter / linter are already there).
More details: https://github.com/flow-php/flow/releases/tag/0.38.0
Flow #PHP got a new website for 0.37.0 release!
This time the bright orange and blue colors were replaced with more toned versions of dark purple. Glowing effect around code samples was also removed.
https://flow-php.com/ new version is up and running.
There is also a new dedicated issue type for website related issues / feedback / requests at https://github.com/flow-php/flow/issues/new?
template=website.yml
That's awesome! I'm so glad to hear that! 🥰
Once you switch your mindset from typical PHP Object/Functional oriented approach to more tabular one, similar to how you deal with excel sheets, data frames becomes way more intuitive 😁
Flow #PHP 0.33.0 was just released 🎉
This update was mostly about stabilization of flow-php/telemetry package and bug fixes.
Please find a full list of changes at: https://github.com/flow-php/flow/releases/tag/0.33.0
I see two niches in the PHP ecosystem. One of them is data processing, and the second is observability. OpenTelemetry is an amazing concept, but the PHP implementation is not really aligned with how PHP and PHP apps work.
Below comes from flow-php/telemetry and #Symfony Bundle
Already using Monolog? Want unified observability without rewriting your logging code?
flow-php/monolo-telemetry-bridge : connect Monolog to the flow-php/telemetry stack with one handler.
Your existing logs flow into the same pipeline as traces and metrics. Automatic trace context propagation (trace_id/span_id attached to every log). Exceptions in Monolog context? Automatically captured with stack traces. Keep your Monolog API, gain better visibility of your system.
On top of that bundle is injecting telemtry into the most popular symfony services like:
Flow on the other hand provides native telemetry integration through:
And I'm also working on adding it into:
Working with PHP, PostgreSql and Symfony?
You might want to check https://flow-php.com/documentation/components/bridges/symfony-postgresql-bundle/
- query builder with full syntax support
- migrations
- define your schemas in php/yaml
- SQL AST Parser
- Client that supports static analysis types narrowing
Flow #PHP #Postgresql will support PostgreSql 18 since relase 0.39.0 💪
flow-php/postgresql
- AST parsers / deparser
- migrations
- query builder covering whole pgsql syntax
- integrations with phpunit / symfony
- AST based paginators / query modifiers
Flow #PHP Symfony PostgreSQL Bundle now supports excluding specific database objects from migrator diff generator by custom exclusion policies
flow-php/telemetry (#PHP implementation of #OTEL) faced an architectural issue tied to the php nature (single thread/process).
https://github.com/flow-php/flow/issues/2348 explains how I'm tackling it, without making Exporters blocking