In this post, we’ll go over a complete workflow for continuous integration (CI) and continuous delivery (CD) for infrastructure as code (IaC) with just 2 tools: Terraform, and Atlantis. This post originally appeared in the 2nd Watch Company Blog. What is Terraform? So what is Terraform? According to the Terraform website: Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions.
When IT organizations adopt infrastructure as code (IaC), the benefits in productivity, quality, and ability to function at scale are manifold. However, the first few steps on the journey to full automation and immutable infrastructure bliss can be a major disruption to a more traditional IT operations team’s established ways of working. One of common problems faced in adopting infrastructure as code is how to structure the files within a repository in a consistent, intuitive, and scaleable manner.
Here are the slides from my BarCamp Philly 2017 talk “All About DevOps”. We got into what the DevOps movement is, what benefits it can bring, and touched on how you might get started at your organization.
Way back in November, I gave a talk at BarCamp Philly. BarCamp Philly is a local unconference and one of my favorite events in the Philly tech community. If you’re in Philly, or a few hours’ drive away, you should definitely check it out. There’s all kinds of talks on all types of subjects, from the technical to the decidedly non-technical. In the talk I gave, I coined the phrase “Bronze Bullet Architecture” to describe my technical approach to building message-based, domain-driven line of business software, and explained you how my professional experience helped me arrive at this style.
Some of the toughest requirements to model in enterprise development are business rules that involve the dimension of time. In this post I’ll show you how to fulfill those types of requirements in an elegant, testable, and scalable way using a message-driven style with NServiceBus.
If you’re familiar NServiceBus and specifically its sagas feature, you can check out the code on GitHub. Of particular interest would be the saga and its tests. There’s also a console app client that will let you play around.
For developers using Entity Framework, unit testing code that depends on the
DbContext class is not the easiest thing. If we’re interested in doing unit testing, we need to be able to use an in-memory (“fake” in Martin Fowler’s terminology) version of
DbContext comprised of lists of objects so that our tests do not hit the database. This series of posts takes you through my process in getting to a facade on top of Entity Framework that results in testable code and tests that are fast to write.
I attended the DotNetFringe conference in Portland in April, and I met some some fantastic people, learned a ton, and had an overall great time. The conference was focused on open source in the .NET ecosystem, and I’m definitely a fan of both of those things.
I find myself in the incredibly fortunate position of having a skill set that is greatly in demand. I get calls and emails on a near-daily basis from recruiters for all types of jobs. (If you don’t think that having recruiters contact you on a daily basis is a good problem to have, I would advise you to consider the employment circumstances of anyone else who is not a medical or IT professional, i.e. the other 99.999% of the world.) While there’s a lot to like about my current position, it would be foolish to be closed to new opportunities if the right one comes up. But how do I now what “the right opportunity” looks like? My answer: The Josh Test.
At work, I use a MacBook Pro and boot into Windows directly using BootCamp. I tried using VirtualBox but key bindings not matching up drove me nuts and I was trying to get a project launched on a tight deadline, so I went with what I knew.
As a reward for launching said project, I got myself a nice new MacBook Pro for home use with a Retina screen, and 16 GB RAM. Professional tools for a professional developer and whatnot.
In my view, there’s 2 main principles that distinguish Domain-driven design as an approach to solving problems:
- All solutions to problems are framed in terms of the value delivered to the stakeholders for the effort required.
- The core of the code is a model of the business process, and it evolves with time as the developers’ understanding of the business with time.