How to Get Rid of Microservices?
Many medium-sized companies have realized that they harm themselves with overengineering by using microservices. What now?
Many medium-sized companies have realized that they harm themselves with overengineering by using microservices. What now?
Hi, Dave Thomas never tires of mentioning that “agile” is an adjective - and not a noun. It is not capitalized. The legendary document we have been referencing for nearly a quarter of a century is not called “The Agile Manifesto.” It is called the “Manifesto for Agile Software Development” . 👈 Agile is not something that can be bought. The manifesto describes how to develop software in an agile (as an adjective!) manner. It does not describe a product.
Hi, Ten years ago, most companies were still dealing with manually managed infrastructures. Today, many medium-sized businesses still find themselves in the same situation. But that comes at a cost - and I’m feeling it right now. The Ghosts of Differences It’s astonishing how often we chase ghosts simply because our environments differ. This ranges from obvious things like available CPU or RAM to subtler issues like different kernel versions or configuration disparities in applications. It gets especially tricky with external application servers, where configuration files are spread throughout the system and can easily drift apart.
Hi, In one of my client projects, we reflect on our working methods. Like most mid-sized projects out there, Scrum is used here too. But we have a few problems: - Sprint goals are never met - Not a sprint goes by without a new task coming in from the side - Estimations are regularly far from reality - Collaboration with other external parties is partially not integrated - … I can certainly think of more examples
Small and medium-sized enterprises (SMEs) often attempt to mimic large corporations and may not realize the harm they inflict on themselves through overengineering.