InfoQ Homepage Development Content on InfoQ
-
What’s new in Groovy 2.0?
The newly released Groovy 2.0 brings key static features to the language with static type checking and static compilation, adopts JDK 7 related improvements with Project Coin syntax enhancements and the support of the new “invoke dynamic” JVM instruction, and becomes more modular than before. In this article, we’re going to look into those new features in more detail.
-
Implementing Aggregation Functions in MongoDB
In this article, authors Arun Viswanathan and Shruthi Kumar discuss how to implement common aggregation functions on a MongoDB document database using its MapReduce functionality. They also discuss a typical application of aggregations which includes business reporting of sales data.
-
Testing SQL Server Code with TST
Automated Testing (unit/integration) is an integral part of any agile development process. However a project with significant logic housed in database code creates severe constraints to writing unit level tests, especially if it is large, complex and depend on data. We will explore the TST framework and a few ideas for writing and maintaining good tests for database code.
-
Interview with Alessandro Del Sole, Author of LightSwitch Unleashed
Visual Studio LightSwitch is Microsoft’s attempt to offer a tool that people with little or no programming experience to create simple and effective line-of-business applications. We spoke with Alessandro Del Sole, author of Microsoft Visual Studio LightSwitch Unleashed, to get some more insights into the product.
-
DevOps:Evolving to Handle Disruption
With continued concerns regarding IT’s ability to meet the demands of the business in light of disruptive influences and a changing economic landscape DevOps might hold an answer.
-
A Look At Elemental Design Patterns
Jason McC. Smith speaks with InfoQ regarding his new book, "Elemental Design Patterns", and details his approach to evolving how design patterns are documented.
-
Data Modeling: Sample E-Commerce System with MongoDB
The rich document capabilities and atomic operation guarantees in MongoDB makes it possible to model many different applications. Even rigorous requirements of conventional applications like e-commerce system are possible in a document database. This data model (i.e. "schema design,") is useful for developing applications around any restricted resource system, not just e-commerce systems.
-
First Steps in Unit Testing
Unit testing goes hand in hand with other agile practices, so starting to write tests is a stepping-stone for organizations wanting to go agile. The road is long, but is worth taking. In this article, Gil Zilberfeld cover tips on what to expect, and steps to take when starting out in order to make unit testing a part of development life.
-
CAP Twelve Years Later: How the "Rules" Have Changed
The CAP theorem asserts that any networked shared-data system can have only two of three desirable properties (Consistency, Availability and Partition Tolerance). In this IEEE article, author Eric Brewer discusses how designers can optimize consistency and availability by explicitly handling partitions, thereby achieving some trade-off of all three.
-
Interview with Mathew MacDonald, Author of Pro Silverlight 5 in C#
We spoke with Matthew MacDonald about Silverlight’s role in the developer’s toolbox and how that role is shifting from cross-platform development to line of business applications. Also covered are some of the highlights from Silverlight 5 and a sample chapter on Silverlight animation from his book.
-
Writing a Comprehensive Unit Test
A common theme amongst people professing “best practices” for unit tests is that you should only write a single assertion for each test. People who make these proclamations rarely show any unit test and those that do only show one. Yet this pattern may require a dozen other unit tests to ensure quality for even a trivial operation. This article uses examples to question that recommendation.
-
Designing and Developing Cross-Cutting Features
Every developer has had to integrate with another system, API or component at one point or another. And, often, a business feature must span systems. If you’ve been on a project like this or have one in the pipeline then this article provides strategies to handle the change. Also, this article covers separating system boundaries and what that means for your technical design.