Spout VS Deptrac

"This project has been archived and is no longer maintained. No bug fix and no additional features will be added. You won't be able to submit new issues or pull requests, and no additional features will be added" https://github.com/box/spout

We were testing PHP Spreadsheet and Spout (https://github.com/box/spout). We chose Spout because of its low memory footprint. It is using streams so it is much lighter than PHP Spreadsheet, although it is missing quite a bit of features that PHP Spreadsheet has.

The Simple Excel package uses the box/spout package under the hood. In the readme it states that you can get to the underlying writer using ->getWriter().

box/spout: Read and write spreadsheet files (CSV, XLSX and ODS), in a fast and scalable way

If you don't have a lot of formatting requirements beyond just the placement of the data in the correct fields, I really enjoy Box/Spout (https://opensource.box.com/spout/), and they have a way to install it without composer.

I've also had good experiences with https://github.com/box/spout

to add to this, this library is really good when wanting to parse CSV files https://github.com/box/spout

Deptrac

Deptrac: Keep your architecture clean.

So far I've found some tools which I could piece together to accomplish enforcing module boundaries, probably run as part of an automated github action. - https://github.com/qossmic/deptrac Uses YAML to define any boundary, you can also use @internal to hide implementation classes. Seems like a good way to achieve what I want.

How about https://qossmic.github.io/deptrac/ ?

>I wonder: Is automatic DI even helpful? You save some lines of boilerplate but sacrifice control over the initialization-order and get a flat, messy, implicit dependency graph

Initialization order doesn't matter if your services are stateless. At least in our codebase, all of them are stateless, as it greatly simplifies reasoning about concurrent code (both in-process and between servers). Yes, it's easy to end up with a very a convoluted dependency graph under the hood, but I don't think it's a problem you really should care about. I mean, your code most likely already compiles to a very convoluted mess of machine code under the hood (with all the optimizations, ABI quirks etc.) and I doubt it matters to you much, as long as it does its job well and doesn't hinder your productivity.

If you are talking about messy dependency graphs from the architectural standpoint (someone can easily add a dependency in the constructor without thinking about the consequences), we use deptrac for our PHP monolith which can validate your architecture is clean at build time [0]

However, for our microservices written in Go, we decided to use manual DI to stimulate developers to prefer simpler design, otherwise our microservices could quickly turn to monoliths again.

[0] https://github.com/qossmic/deptrac

Deptrac is a static code analysis tool for PHP that helps you communicate, visualize and enforce architectural decisions in your projects.