Jan Blaha

Blog about software development

architecture

 
12-03-2013 20:56 architecture testing .NET

In the last post it was explained how to prepare unit test hierarchy for writing tests interacting with database. In this post I will concentrate

read more


03-18-2013 20:56 architecture testing

In the last post was proposed using state testing rather than behavior mock testing when it’s not necessary. This means testing results of methods

read more


03-10-2013 14:56 architecture testing

Using mocks and behavior testing is a great idea. Especially when you are dealing with complicated dependencies and business logic. But some

read more

last blog posts


09-10-2015 14:09 AWS

Such a very common thing like adding an existing external volume to Amazon elastic beanstalk is not easily supported out of the box. The official blog mentions only how to attach a snapshot or how to attach and overwrite a new volume every time the service starts. It took me a while to make the config file actually adding an existing volume without formatting it every time so I share it here with you...

read more

04-10-2015 14:09 jsreport

The best practice when adding email notifications feature to your system is to separate as much as you can from email body assembling to email sending outside of the core system. The emails templates quite likely often changes and you don't want to deploy the system because of every single notification change. The best is to just separate everything into an external system and give the access to your PR or Marketing department so they change emails as the time goes without affecting the core system.

read more

03-22-2015 14:09 .NET NHibernate

NHibernate still rocks! Even with quite a bit old code base it is still at the top of the c# frameworks we daily use. Especially the framework extensiblity is tremendous. Now I am going to show you how we use NHibernate in the multitenant fashion.

read more

Jan Blaha

About author

Hi! My name is Jan Blaha. I'm software developer and startup enthusiastic. See my current work.