Building a Two-Stack CMS for a global product catalog
We build many websites with rich content, often using popular Content Management Systems (CMS). A recent project involved a marketing website for a global manufacturer which demanded complex interactive content with high availability and traffic needs. <br/> Our response was to apply the editing-publishing separation pattern and build two distinct stacks of software for content creation and delivery. In this deck you can see an overview of this architecture and our response to the issues of integration between the stacks, providing a secure preview of the live site, and handling the evolution and scaling of the system.
Use structured logging for log search and analytics
Logging is being followed in software development since long. Structured logging provides meaning to logs and helps not only just for debugging, but for reporting, monitoring and alerting, performance benchmarking and with analytics as well.
Guidelines for Structuring Automated Tests
In every project, these questions come up - what kind of automated tests should we write? What is the right level of testing? How much of test coverage is "good enough"? I would like to share guidelines that I've found to be useful for planning and building test automation suite for my project.
Using TDD to Influence Design
After hearing the discussion about TDD by Martin Fowler, Kent Beck and DHH. I thought of putting down my 2 cents about TDD - why I follow it, and why I find it useful as a thought process for solving design problems.
Zero downtime using blue-green deployment strategy
Zero downtime during application deployment is one of the key requirements for continuos delivery. And no business would like their site to be down and showing maintenance page every few days/weeks during deployment.
Building highly scalable and performance application using non-blocking architecture
Article shows the modern way of building websites using non-blocking architecture pattern. Why this style of architecture is beneficial and what are the frameworks available to implement.
Cross functional requirements
It is always been difficult to identify stories for cross functional requirement (XFR) a.k.a NonFunctional requirements (NFR) during inception (2-3 weeks of project kick-off/initiation phase). Here is the technique to do that in short 2-3 weeks project inception.
Why responsive web design?
Objective of this blog post is look into the history and learn what problem we try to solve with RWD.
Data Anonymization techniques, Blacklist and Whitelist?
In this post I describe the two techniques used for data anonymization, Blacklist and Whitelist. Blacklist is easy to implement and get started, whereas Whitelist is more secure and preferred.
Data Anonymization, need for every site in production
Afraid of getting production data due to privacy issues. Data Anonymization tool can help you to build anonymized production data dump to use for performance and security testing, debugging production issues and development purpose.