The Canonical Protocol design pattern is one of the inventory standardization patterns that aims to elevate the composition-centric characteristic of SOA by making services interoperable with each other. By enforcing the use of a common communication framework, it eliminates the need for protocol bridging and increases the reusability and the recomposability potential of services in a service inventory.
James Mathewson gets a lot of questions about what it means for the reader to be in control. In this article, he unpacks this truth in terms of a user behavior that is common and growing in digital media.
Jez Humble, coauthor of Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, urges teams to move away from the all-or-nothing design of traditional software delivery approaches. Following the practices outlined here, you can deliver single-feature or small-story batches that dramatically decrease the time needed to build a new product or new release, testing and moving forward on successful features and redesigning or dropping features that fail (or that users show they don't really want).
This chapter from 100 SOA Questions answers the questions,
what is SOA, is SOA an architectural style, what are fundamental constructs (the DNA) of SOA, what is the difference between a Web Service and an SOA service and what makes a project an SOA implementation?
The Enterprise Inventory design pattern attempts to maximize the reusability and recomposition of services by proposing the development of services based on a single enterprise-wide service inventory.
This chapter introduces you to the basics of using Xcode to build your projects. You see how to build a simple Hello World project, compile and test it in the simulator, and then learn how to compile for and deploy to the device. You also discover some basic debugging tools and walk through their use as well as pick up some tips about handy compiler directives. This chapter also looks at how to submit to the App Store and perform ad hoc distribution for testing.
Rex Black and Capers Jones continue discussing Capers Jones' book The Economics of Software Quality. Watch this podcast to learn some surprising and motivating facts about software quality and how to improve it.
The end of 2011 brought new releases of both the C and C++ standards for the first time, with C11 sneaking in just before Christmas. David Chisnall takes a look at one of the more important features added to both standards: atomic operations.
Gary McGraw and Sammy Migues clarify the intended use of the Building Security In Maturity Model (BSIMM) and compare it to the SAFECode Practices methodology.
Enterprise development and networking specialist Stephen B. Morris illustrates how to handle a classic C/C++ problem by using the new features in C++ 11 in conjunction with more established techniques.
Gary McGraw and Sammy Migues introduce a revised, compact version of the BSIMM for vendors called vBSIMM, which can be thought of as a foundational security control for vendor management of third-party software providers.
This chapter includes case studies to illustrate the effectiveness of SONAR, a content distribution model designed to improve ROI on existing web content.
Get a brief overview of the various Drupals (the project, the websites, and the association) and what they mean to you. You'll also see some examples of Drupal in action and get an overall look at how Drupal works.
Ronald D. Reeves, Ph.D. proposes a new advanced classification in the software field: the System Software Engineer. Although many engineers may really want to continue up the technical path, the available classifications don't provide sufficient monetary rewards for the effort.
The end of 2011 brought new releases of both the C and C++ standards for the first time, with C11 sneaking in just before Christmas. David Chisnall takes a look at one of the more important features added to both standards: atomic operations.
The Service Layers design pattern attempts to standardize the way services are designed within a service inventory by organizing services into logical layers that share a common type of functionality. By structuring the service inventory around common types of functionalities, this design pattern eases the evolution of services and reduces their governance burden.