Suchergebnisse
Suchergebnisse:
1. Aug. 2019 · Agile Development. Plan-driven engineering expects us to come up with a predictive plan that precedes development. The plan lays out the people, resources and timelines for the overall project. Software design is also done up-front, with implementation expected to conform with this design.
21. Aug. 2019 · Microservices Guide. In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully ...
My email address is martin@martinfowler.com, but if you do email me please read my FAQ first. Email is the best way to reach me. Pronouns. he/him. Social Media. I'm not particularly active on social media, although I do post updates using various social media accounts. Mailing Address. Martin Fowler. Thoughtworks. 200 E. Randolph, 25th Floor
Each book should be an excellent, in-depth coverage of its topic. Each topic should be relevant to hands-on technical leaders, particularly in enterprise applications. The books should focus on long-lived fundamentals: knowledge that doesn’t age much even as technology changes. All these criteria mean the books are worth the investment of a ...
3. Aug. 2004 · object collaboration design. In my view the Gang of Four is the best book ever written on object-oriented design - possibly of any style of design. This book has been enormously influential on the software industry - just look at the Java and .NET libraries which are crawling with GOF patterns. Despite my praise, this is not an easy book to read.
3. Juni 2015 · I've heard different ways to execute a monolith-first strategy. The logical way is to design a monolith carefully, paying attention to modularity within the software, both at the API boundaries and how the data is stored. Do this well, and it's a relatively simple matter to make the shift to microservices.
2002. This book started after Dave Rice and I gave some talks on J2EE architecture and mulled over how the concepts we had learned in C++, Forte, CORBA, and Smalltalk had been crucial to us developing good designs in Java. With this book I wanted to set many of these patterns down to help developers whatever their platform.
