InfoQ Homepage Web Development Content on InfoQ
-
/articles/Netter-on-Rails/en/smallimage/image_net_learn_ruby.jpg)
Why Would a .NET Programmer Learn Ruby on Rails?
.NET developer Stephen Chu gives us some insight into his transition to Ruby on Rails programming. Quote: "By being loyal to one technology stack, I am bound to unconsciously make biased decisions, which will ultimately hinder my ability to deliver business value."
-
/articles/Agile--The-SOA-Hangover-Cure/en/smallimage/image_soa_hangover.jpg)
Agile: The SOA Hangover Cure
Author Carl Ververs who is an expert on SOA Integration and Distributed Systems writes about the application of "Agile" development philosophies that ensures that organizations can overcome architectural paralysis and get moving on those important SOA projects, while at the same time ensuring that the architecture is sufficiently flexible and adaptable for future growth.
-
/articles/Rule-Engines/en/smallimage/ruleengines.jpg)
Real-World Rule Engines
For many developers, rule engines are buzzwords, or black boxes on an architectural diagram: something to be feared or admired from afar, but not understood. In this article, Geoffrey Wiseman shares his practical experience with rule engines and with Drools in particular to support in-market solutions for financial services.
-
/articles/Evolutionary-integration/en/smallimage/esbsmall.jpg)
Evolutionary integration with ESBs
ESB Programming experts provide simple working examples and clearly communicated ideas and patterns using the open source Mule ESB tool set. These examples provide both working code as well as suggest a methodology of evolutionary integration which can be used to dramatically simplify and accelerate SOA integration.
-
/articles/Brasilian-Healthcare-System/en/smallimage/newmedical.gif)
Casestudy: Brasilian National Healthcare System
This casestudy takes a detailed look at the implementation and architecture behind the Brasilian National Healthcare System, a 2M line of code, truly mission critical Java application. Lessons learned, best practices, and details down to the interaction diagram are covered