- The History of Version Control (Francis Irving) — concise history of the key advances in managing source code versions. Worth it just for the delicious apposition of “history” and “version control”.
- A Look Inside Mobile Design Patterns — Sample chapter on how different apps handle invitations, from a new [O’Reilly-published, huzzah!] book on mobile design patterns. (via David Kaneda)
- Node Toolbox — concise compendium of resources for node.js development.
"design patterns" entries
Migrating to cloud-native application architectures leads to innovation.
Editor’s note: this is an advance excerpt from Chapter 1 of the forthcoming Migrating to Cloud-Native Application Architectures by Matt Stine. This report examines how the cloud enables innovation and the changes an enterprise must consider when adopting cloud-native application architectures. Also, Matt will be conducting a two-day intensive training on the fundamentals of cloud-native applications at our Software Architecture Conference happening March 16-19 in Boston.
Let’s examine the common motivations behind moving to cloud-native application architectures.
It’s become clear that speed wins in the marketplace. Businesses that are able to innovate, experiment, and deliver software-based solutions quickly are outcompeting those that follow more traditional delivery models.
In the enterprise, the time it takes to provision new application environments and deploy new versions of software is typically measured in days, weeks, or months. This lack of speed severely limits the risk that can be taken on by any one release, because the cost of making and fixing a mistake is also measured on that same timescale.
Internet companies are often cited for their practice of deploying hundreds of times per day. Why are frequent deployments important? If you can deploy hundreds of times per day, you can recover from mistakes almost instantly. If you can recover from mistakes almost instantly, you can take on more risk. If you can take on more risk, you can try wild experiments—the results might turn into your next competitive advantage.
The elasticity and self-service nature of cloud-based infrastructure naturally lends itself to this way of working. Provisioning a new application environment by making a call to a cloud service API is faster than a form-based manual process by several orders of magnitude. Deploying code to that new environment via another API call adds more speed. Adding self-service and hooks to teams’ continuous integration/build server environments adds even more speed. Eventually we can measure the answer to Lean guru Mary Poppendick’s question, “How long would it take your organization to deploy a change that involves just one single line of code?” in minutes or seconds.
Imagine what your team… what your business… could do if you were able to move that fast!
Find out if mediator or broker topology is right for you.
Editor’s note: this is an advance excerpt from Chapter 2 of the forthcoming Software Architecture Patterns by Mark Richards. This report looks at the patterns that define the basic characteristics and behavior of highly scalable and highly agile applications, and will be made available to download in advance of our Software Architecture Conference happening March 16-19 in Boston.
The event-driven architecture pattern is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. It is also highly adaptable and can be used for both small and large, complex applications. The pattern is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.
The event-driven architecture pattern consists of two main topologies, the mediator and the broker. The mediator topology is commonly used when you need to orchestrate multiple steps within an event through a central mediator, whereas the broker topology is used when you want to chain events together without the use of a central mediator. Because the architecture characteristics and implementation strategies differ between these two topologies, it is important to understand each one to know which is best suited for your particular situation.
Let the environment do more of the work
Functional programming keeps growing. While it has long been a popular topic in academic circles, and many of my CS-educated friends wonder why it took me so long to discover it, the shift in approach that functional programming requires made it a hard sell in the commercial world. As our computers have become more and more powerful and our problems more complex, functional programming approaches and environments seem better able to shoulder those loads.
Neal Ford, Meme Wrangler at ThoughtWorks, has been showing developers how to shift from classic imperative models to cleaner functional approaches. I was lucky to get to talk with him at OSCON, and we’ve also posted his OSCON talk, with many more concrete code examples.
An interview with Rick Copeland, the author of MongoDB Applied Design Patterns
At a recent MongoDB SF event, I had a chance to meet Rick Copeland. He was in town and stopped by the event to sign copies of his book, MongoDB Applied Design Patterns. While I am not Rick’s editor, I approached him to see if he would be okay with me filming the book signing as well as participating in a follow-up written interview. He agreed. It was great to catch a bit of footage of the event as well as have a chance to ask Rick about how he started working with MongoDB, why he wrote the book, and how he balances a busy schedule filled with working, writing, and speaking.
How did you get started working with MongoDB?
Rick Copeland: I started using MongoDB at Sourceforge in 2009. Just before I came on board, the decision had been made to base the next generation of SourceForge on MongoDB instead of relational databases. The driving factors behind this decision were some internally-conducted benchmarks and a developer love of the document-oriented model.
Design patterns for PHP
William Sanders (@williebegoode) is a Professor of Interactive Information Technology at the University of Hartford and author of over 40 technical books! His latest book with us is Learning PHP Design Patterns. We recently sat down to talk about design patterns and how they can help create reusable code and save you valuable time. You can also check out more from Bill at his website.
- Why use design patterns for PHP? [Discussed at the 0:28 mark.]
- Big programs and lots of code can become unwieldy [Discussed at the 2:06 mark.]
- Mobile devices and PHP design patterns [Discussed at the 5:30 mark.]
- Bill talks common design patterns and how they help [Discussed at the 7:25 mark.]
- How to start using design patterns with PHP [Discussed at the 10:15 mark.]
You can view the entire interview in the following video:
Version Control, Web-based ID, Mobile Design, and Node.js Tools
- Android Patterns — set of design patterns for Android apps. (via Josh Clark on Twitter)
- Preview of Up and Running with Node.js (O’Reilly) — Tom Hughes-Croucher’s new book in preview form. Just sorting out commenting now. (via Tom on Twitter)
- #Blue Opens for Business — a web app that gets your text messages. You can reply, and there’s an API to give other apps read/write access. Signs the text message is finally becoming a consumer platform.