Has your project gotten to the point when big data sets and/or time-consuming calculations have begun to affect performance? Or are you struggling to optimize your queries and need to cache some information to avoid continually hitting your database? Then caching could be your solution.
For this article, I will demonstrate how to utilize Amazon ElastiCache for Redis to speed up areas of your application. The example application we will build uses Spring Boot 2.x and is available on Github.
The term “technical debt” was coined over a decade ago to help highlight a common problem in software development. Generally you can think of technical debt like this:
The cost of additional rework created by choosing an easy, shortcut solution now instead of the better approach that would take longer.
Delivering software to meet deadlines or functional goals that are wrought with technical debt is like buying items before you can afford them. Both practices can drastically affect your ability to reach your future goals, both long term and short term.
This article is a gentle reminder to recognize, fix, and avoid technical debt in your software projects.
Opinions on the emerging Virtual Reality market vary. One one end, there are those who say it’s just a gimmick and will pass shortly. On the other end, there are those who herald it as the birth pangs of a paradigm shift in how we interact with technology.
I sit somewhere in the middle. I own an HTC Vive and it is pretty dang awesome. The experience is not perfect, of course, but with interest growing and prices coming down, it’s just going to get better.
One expression of VR’s growing popularity is that Unity3D supports VR programming. And, with the free VRTK (Virtual Reality Tool Kit) framework, it’s becoming much easier to get started programming for VR. VRTK implements many basic components, such as various movement implementations, object interaction, and projectiles.
Working on a fun little side project, I noticed one implementation it did not have: a virtual reality bomb. So, I set upon to create one myself. This post details the process I went through for creating a timed, throwable, explosive object for virtual reality using Unity3D & VRTK.
Tl:dr: Use Event Storming to rapidly gain group understanding of complex business domains while having a more enjoyable time.
While I was browsing tech news sites looking for articles, a headline caught my eye talking about domain-driven design (DDD). Its main idea was to implement Event Storming to drive the understanding of the business domain. The more I read about it, the more I saw the value in what Event Storming offered.
On a recent consulting project, we were piloting Agile in a Waterfall environment, so in reality, any requirement gathering process used would have been new. We chose to compare Event Storming to User Story Mapping, allotting just one hour to work with each process. The process that the pilot Agile team favored would then be used going forward.
In this blog, I will share the main takeaways and benefits that became apparent while implementing Event Storming sessions, especially as compared to User Story Mapping. I will first explain the project we worked on and underlying opinions that drove our trial, what key aspects of Event Storming stood out to us, and then tips I picked up along the way for effective Event Storming sessions….
This article is part of a series of articles about modern tooling and techniques for building distributed systems in DotNet.
In our first article, we saw how easy it was to set up a full ELK stack by leveraging pre-built containers. In this blog, I show how to leverage ELK in a .NET application and aggregate our logs into a single place. You will see just how simple it is to start getting some insights into your application. Let’s get started…