Just finished my presentation on Open source and Architecture in the Wellington Software Architect Forum.
We have covered these topics:
1) Definition, Licensing & players
2) Open source based architecture examples
3) Best practices
4) ROI, TCO and other TLA
5) Open source tools for architecture
6) Want to be an open source developer?
7) Future FOSS trends
You can download the presentation here.
The following happens in many software projects -
At start, it seems you only need one environment for your web application, well, at most two:
One development environment (AKA your PC) and one server.
But as time pass, you find you need additional environments:
The clients might want their own testing environment, sometimes you need to have a pre-production environment or a staging environment, so business managers can approve the ongoing content as well as look & feel.
Do you really need these environments? What are these environment good for?
Here is a short description of some of the more popular environments and their purpose.
After a session I gave about Scalability in Wellington NZ, one of developers asked me what are the things software architect should consider. I have gathered and compiled this list:
Application security encompasses measures taken throughout the application's life-cycle to prevent exceptions in the security policy of an application or the underlying system (vulnerabilities) through flaws in the design, development, deployment, upgradation, or maintenance of the application. [1]
If this was a comics style blog it would start like this:
They both stood there, the clean and virtues super-hero MVC and his arch-enemy the dirty and corrupt spaghetti-design-pattern... they were both aware that only one of them will prevail.
When designing enterprise application architecture, talking to clients and doing interviews for my group, I sometimes tackle the “scale up vs. scale out” software architectural dilemma.
To set the stage lets define what scale means as well as what scale-up and scale-out mean.
