Posted by Gero Vermaas in the early afternoon: July 28th, 2010
This is the tenth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The tenth principle we discuss is called “Architecture emerging from Projects“. (more…)
Posted by Reint Jan Holterman in the early evening: July 26th, 2010
Recently, Andrew Phillips, VP of Product Management at XebiaLabs, and I had the opportunity to speak with Mike Vizard, tech journalist for IT Business Edge. We had a great conversation about automating application deployments and Mike’s article provides a nice look into our discussion.
(more…)
Posted by Gerbrand van Dieijen at around evening time: July 25th, 2010
People use metaphors to understand or to explain something better. Metaphors in software development are ubiquitous, as in the computer world in general. Especially people who are in the business of software development, but aren’t experienced in actual software development, often use various metaphors to better grasp what they’re dealing with. Some metaphors work, but many are more damaging then helpful.
In this posting I’ll list a few metaphors I, as a software developer, heard in recent years, starting with rather ill-chosen or understood metaphors.
Posted by Jan Vermeir mid-afternoon: July 22nd, 2010
In an attempt to better understand the ideas behind ‘Life Beyond Distributed Transactions, an Apostate’s Opion.’ by Pat Helland, I’m going to try to explain how the concept would work out for a time-honored example: the good old transfer of money from one account to the other, the archetype of all distributed transactions because we want to make absolutely sure we don’t lose money.
(more…)
Posted by Sander van den Berg in the early evening: July 21st, 2010
This is the ninth post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The ninth principle we
discuss is “Comprehensible over Comprehensiveness”.
Posted by Wilfred Springer in the early afternoon: July 21st, 2010
How did we end up here?
Fifteen years ago, at the end of the two-tier client server age, people started to realize the importance of distinguishing between at least three different layers in the architecture. A business layer, providing a convenient API allowing you to address a particular business concern, a data layer storing related data, and a presentation layer providing a convenient user dialog on top of the business logic.
Posted by Denis Koelewijn in the early morning: July 15th, 2010
This is the eight post in a series of blog posts discussing Lean Architecture principles. Each post discusses one principle. Applying these principles results in an architecture (process) that is better connected to the business, better able to deal with change and more cohesive. The eight principle we discuss is called “Focus on the value stream“. (more…)
Posted by Andrew Phillips mid-afternoon: July 5th, 2010
Sometime in the bright future, you will be able to deploy the same virtual appliance containing your application to all your target environments without adjustments. For the time being, however, deployments to traditional DTAP1 landscapes almost always mean “tweaking” the application and associated configuration and resources to match the target environment – think endpoints, properties files or datasource usernames and passwords, to name but a few.
In the absence of any established standards or even guidelines in this area, many different solutions to this problem of deployment package customization have been employed, from fairly elegant approaches such as JMX to crude string search-and-replace.
Furthermore, different types of middleware platforms have varying degrees of support for customizations: typically, portals, ESBs and process servers offer some “native” solution to the problem, whereas application servers tend to leave users to fend for themselves.
More often than not, the result is a chaotic mix of customization approaches across projects, target platforms and departments2. Here, we’ll look at some of these approaches, classify them and examine some drawbacks and benefits. (more…)
Categories
- Java (311)
- Agile (181)
- General (136)
- Scrum (67)
- Architecture (64)
- Testing (59)
- Performance (46)
- Middleware (55)
- Deployment (37)
- Xebia Labs (38)
- SOA (31)
- Podcast (31)
- Project Management (28)
- Tools (25)
- Uncategorized (20)
- lean architecture (20)
- Quality Assurance (17)
- Articles (13)
- Virtualization (19)