An architect I was recently speaking with at work mentioned an architectural approach to designing our systems to make them highly available and independently scalable based on the resources used. This concept is called control plane and data plane.
The control plane and data plane concept is worth considering if you deal with high traffic volumes where being highly available is a priority.
In the past, I’ve run into trouble running integration tests against docker containers. Let me give you a recent example, I’ve been working with AWS DynamoDB, when it comes to testing, I don’t want to run my integration tests against either a real or a mocked DynamoDB table. It just so happens that AWS provides us with a DynamoDB docker image, this allows us to spin up a local instance of DynamoDB inside a Docker container.
In this blog post we are going to look at the Put and Get DynamoDB operations. First we will look at how to Add ‘Put’ an item onto a DynamoDB table, then cover how we ‘Get’ either a single item or all items from a DynamoDB table.
If you haven’t already read my previous blog post on Creating an AWS DynamoDB Table in .NET Core that is a good place to start. We covered creating a DynamoDB client and assigned Access and Secret keys to the client. We then used the client to create a DynamoDB table.
Let’s start this post by looking at DynamoDBs PutItem.
Last year, I made the move from QA to Development. I had been a QA for a number of years and due to a number of reasons, I felt like I needed a change.
While I knew the change was going to require dedication and effort, I didn’t quite realise how hard it was going to be.
I made a few mistakes in my transition. This post goes over those mistakes and then looks how I rectified them. I want to highlight my pitfalls to hopefully help anyone else thinking about changing roles, so they don’t have to make the same mistakes I made.
Dependency Inversion is a widely used principle in building software today. While it is heavily used, the understanding of Dependency Inversion, Inversion of Control and Dependency Injection are less well known. These three principles and patterns are often spoken about as if they are the same.