- GETTING THE PROBLEM DOMAIN OF THE DATABASE BACK IN FOCUS FULL
- GETTING THE PROBLEM DOMAIN OF THE DATABASE BACK IN FOCUS SOFTWARE
- GETTING THE PROBLEM DOMAIN OF THE DATABASE BACK IN FOCUS FREE
The Cloud Native Computing Foundation (CNCF) maintains an interactive graphic of the nearly 1,000 unique services that make up the cloud-native ecosystem, many of which are free and open source to boot. “Everything was so much simpler before, not because we made a mistake as an industry, but because the demand of those systems grew so dramatically that we have to ship faster,” said Kaspar von Grünberg, founder of Humanitec, a startup that helps companies build their own developer platforms, in an interview with InfoWorld.
GETTING THE PROBLEM DOMAIN OF THE DATABASE BACK IN FOCUS SOFTWARE
The combined popularity of cloud computing and the open source software movement has seen the number of options available for developers to build and run more scalable, resilient, modular, and updatable applications rise at an inexorable rate. “Getting more engineers to think that way is a challenge.” The downside of choice “Given the demand for software developers today, companies don’t have the leverage to push developers towards a mental model of primarily delivering value to their customers,” Etheridge said.
GETTING THE PROBLEM DOMAIN OF THE DATABASE BACK IN FOCUS FULL
The cloud-native era has ushered in the potential for more accidental complexity than ever before, setting a collision course between developers, who want to leverage the full toolkit available to them, and their bosses, who want them to focus on delivering value to customers. The other area is accidental this is the complexity that comes with our tooling and what we layer on top when solving a problem.” He told InfoWorld, “Essential is the complexity in the business domain you are working in, the fact that enterprises are extremely complicated environments, so the problems they are trying to solve are inherently complex. Justin Etheredge, cofounder of the software agency Simple Thread, helpfully differentiates between essential and accidental complexity. The explosion of choice and the pace of development make it challenging for developers to keep up with the zeitgeist, with many developers getting caught in the headlights.” “While we’ve seen an up-leveling of capabilities that enable developers to do more by using high-level frameworks for application development and machine learning, this comes at a cost. “It has never been more difficult to be a software developer than it is today,” said Nigel Simpson, a consultant and former director of enterprise technology strategy at Walt Disney.
Simply assemble and build your business logic on top. On the other hand, complex technologies have never been easier to consume off the shelf, often through a single API-from basic libraries and frameworks, to image recognition capabilities or even whole payments stacks. Or, as his colleague, head of devops product marketing at AWS, Emily Freeman, said in 2021, modern software development is “a study in entropy, and it is not getting any more simple.” “Was it easier in the days when everything was in a monolith? Yes, for some parts definitely.” “There is a clear increase in complexity when you move to such a pervasive microservices environment,” said Amazon CTO Werner Vogels during the AWS Summit in 2019. Add to that expectations of feature-rich, consumer-grade experiences, which are secure and resilient by design, and never has more been asked of developers. The shift from building applications in a monolithic architecture hosted on a server you could go and touch, to breaking them down into multiple microservices, packaged up into containers, orchestrated with Kubernetes, and hosted in a distributed cloud environment, marks a clear jump in the level of complexity of our software. If Ozzie thought things were complicated back then, you can’t help but wonder what he would make of the complexity software developers face in the cloud-native era. “It sucks the life out of developers it makes products difficult to plan, build, and test it introduces security challenges and it causes user and administrator frustration.”
“Complexity kills,” Lotus Notes creator and Microsoft veteran Ray Ozzie famously wrote in a 2005 internal memo.
0 kommentar(er)
