Sarah Savage logo

A fusion of development and business

Microservices may be dangerous for your team

Last week, Zend by Perforce wrote a blog post about when and how to migrate from a monolithic application to a microservices architecture. For those that haven’t read the post, the TL;DR is that as your application grows, it makes sense to migrate to microservices in order to streamline development. I find this advice to be dangerous, for a number of reasons. Microservices as architecture Microservices were never meant as a purely architectural pattern; rather,… continue reading.

Examples of open source community in action

With as much as has been written about turmoil in the WordPress community, I wanted to take a minute to highlight a contributor in the open source space that truly embodies the open source ethos and a community-driven spirit. Many people who know me know that I have problems with the design of Laravel and I object to things like Active Record and the heavy use of statics and globals. And I know I am… continue reading.

Who owns WordPress, really?

There is a lot of upheaval in the WordPress community right now. There is talk of forks, and community repositories for packages, and lots of different ways that the community can establish independence from the status quo. But who really owns WordPress? I’m not talking about the licensing here – I’m talking about ownership in the sense of who owns the copyright? Who has authority over the code? For every open source project there are… continue reading.

Mental health in tech

I’m not ashamed to admit the fact that I struggle with my mental health. Mental health issues are common among technology professionals. Perhaps this is even more common than in the general population, though I do not have any statistics to back this up. What I can say for certain, though, is that the technology world is not conducive to great mental health: we put incredible pressure on developers to deliver the impossible in unrealistic… continue reading.

Endings in open source

Most projects announce to some kind of fanfare – some greater than others. We love to see a new open source project released, and we cheer when a new package is available that solves a problem, particularly if it’s a problem we’re having. On the other end of the spectrum is the fact that open source packages can sometimes run their course, and need retirement. Such is the nature of a package that I maintain,… continue reading.

Air Traffic Control: Routing microservices with a single Nginx server

In my last post I talked about linking microservices together inside a single Docker network for easy communication between the services. For web developers, this poses an interesting problem: if we want to access the services from our local machines, we need to deal with the fact that we can’t have multiple machines bound to the same port. If you have two microservices running at the same time, both trying to bind to ports 80/443… continue reading.

A Commitment to Community

Last week I attended php|tek in Chicago. During the conference, a number of speakers espoused the value and importance of contributing to the open source community. Ben Ramsey talked about how his contributions to open source didn’t seem to be valued in his most recent job search. He also talked about the value and importance of saving PHP. Michelle Sanver talked about the importance of community and the value in being part of it, but… continue reading.