[slideshare id=44635978&doc=event-sourcingyourangularjsapplications-150213045911-conversion-gate02] Demo code (work in progress) Enjoy
In my previous blog post I explained about the Data Storage Maturity Model and how you would get a much more mature and capable application if you used Event Sourcing. That blog post did bring up some interesting question. Should I always use Event Sourcing? Given that Event Sourcing was at the top of the pyramid you could conclude that you should always aim for the the top and use Event Sourcing. Aiming high is a noble cause and sounds like the right thing but it turns out that it isn’t that simple. If your application is relative simple … Continue reading What is the right level of maturity
There are many ways of storing data when developing applications, some more mature and capable than others. Storing data of some sort or another in an application is common. Extremely common to be exact as almost every application out there needs to store data is some way or another. After all even a game usually stores the users achievements. But it’s not games I am interested in. Sure they are interesting to develop and play but most developers I know are busy developing line of business (LOB) applications of some sort or another. One thing line of business application have … Continue reading Data Storage Maturity Model
In general AngularJS applications are quite fast, specially when compared to more traditional browser based applications that constantly post back to the server. However there are always a few things that will help performance and make an application even faster. Disabling Debug Data Normally AngularJS adds several things like CSS classes and some scope related properties to DOM elements. This is not really needed to run the application and is really only done to help development tools like Protractor and Batarang. When the application is in production that is not really needed and you can save some overhead by … Continue reading Speeding up your AngularJS applications
Testing AngularJS directives usually isn’t very hard. Most of the time it is just a matter of instantiating the directive using the $compile() function and interacting with the scope or related controller to verify if the behavior is as expected. However that leaves a bit of a gap as most of the time the interaction between the directives template and it’s scope isn’t tested. With really simple templates you can include them in the template property but using the templateUrl and loading them on demand is much more common, specially with more complex templates. Now when it comes to … Continue reading Testing an AngularJS directive with its template
[slideshare id=42261188&doc=therawstack-141202084110-conversion-gate02] Online demo: http://rawstack.azurewebsites.net/ Source code: https://github.com/mauricedb/SDC-2014 https://github.com/mauricedb/RawStack
There are two ways to use the angular.module() function. There is the call with one parameter, that returns an existing module and there is an option of using two parameter which creates a new module. The second way, where a new module is created, is perfectly fine and should be used. However the first option, where an existing module is loaded should be considered and anti pattern in most cases and should not be used unless there is an exceptional and very good reason. What is wrong with angular.module(“module”)? Why should this usage be seen as an anti … Continue reading angular.module("module") is an anti pattern
Just so you are aware, the URL with the RSS feed for my blog has changed. Please use the following URL now: http://blogs.msmvps.com/theproblemsolver/feed/ Apologies for the inconvenience.