Blog & News
About YourBase
We need base services and not just microservices
Hi there, I'm Yves. I left Google recently after almost 10 years there as a site reliability engineer. This is part of a series of articles about base services and how they can speed up the development of software. I wrote recently about how the monolith slows down teams with more than 20 or so developers and why many companies are stuck with the monolith. We often talk about microservices but we should be talking more about base services. Base services are components of a fast-changing network that are used as a base for other services and should be highly dependable for both development...
read more
When should you create new microservices?
To move fast, software development teams should use small independently-released microservices. But how small should they be? Microservices are somewhat like camping: the first time you do it, there is a lot of uncertainty and stress. What should you bring in your backpack? You end up overthinking it and bringing many things you don't need. With microservices, we need to choose the right service boundaries: what goes into which service. Sometimes we create too many services that become a maintenance nightmare. And it is tough to course-correct and rearrange the architecture once services are...
read more
Why are so many companies stuck with the software monolith?
In my last article, we covered how the software monolith is the result of a successful software project that delivers good results, causing it to receive more development attention until it becomes too large. It can be frustrating for a large team to work in the same code base Because there are dozens of engineers adding code and dependencies to the same application, builds take several minutes or even hours. Tests are very flaky because they rely on dozens of dependencies that may or may not be working at any given time. Software releases have too many unrelated changes, so they are fragile...
read more