2019 was an inflection point for the open source community. Millions of people across the globe contributed to tens of millions of open source projects last year.
🚀 We help our clients to migrate, build and optimize in the cloud 🚀
If you or your business associates ever have questions or need advice, please send them our way, we would love to start a conversation.
2019 was an inflection point for the open source community. Millions of people across the globe contributed to tens of millions of open source projects last year, nearly doubling from the year prior. The notion of open source adoption is long gone. Open source is inescapable. You adopted it the moment you turn your laptop on. Microsoft (Microsoft!) wasn’t satisfied just being the largest contributor to GitHub, so they bought it. Open source software is the foundation of everything we do today. And, that has made the massive ecosystem that supports our open source world the life force of our industry.
This is great news. But, it has created some unexpected challenges. Documentation has become a particularly thorny one. A typical project includes well over 100 open source dependencies, and many of those dependencies interact with each other. Compatibility is key. But, with even modest open source projects having thousands of contributors and dozens of releases a year, compatibility is also elusive. The web itself tends to be far more durable than the content it stores, and much of the reference material for fast-moving open source projects is out of date. Sometimes annoyingly so, sometimes dangerously so. The resulting toil is real, and it matters. Despite that, open source is still well worth it. We have the wind at our backs. After all, when we need to reconcile conflicting documentation, we can. We have the code.
-Cris
Terraform On a New Cloud - Getting Started
When I started to Terraform and was looking for examples, I found plenty of code showing how to create individual resources or groups of them but not much on how to structure the code for a whole organization. As a software engineer, there are many great examples of how to structure software projects, along with design patterns and principles on how to create extensible but DRY code. Infrastructure projects bring in a variety of new concerns because infrastructure as code is so new, it doesn’t have the maturity that brings with it tried-and-tested philosophies. I endeavor here to lay out what we've found Terraforming dozens of organizations.
This will be a multi-part series, first laying out the basic philosophy and structure of our Terraform repositories, then giving examples of importing existing resources, delineating services into "projects," and adding the automation and safety checks that come with operational maturity. This is the first piece of the series and simply explains that philosophy and structure.
With the endless flood of new products, features and changes from AWS and its surrounding ecosystem, it can be easy to miss an update. Our monthly round up highlights major AWS news, announcements, product updates and behind the scenes changes we think are most relevant.
While AWS manages the Kubernetes control plane for you, it’s (mostly) up to you to manage your nodes. This guide is indeed a comprehensive look at your options.
We use Terraform pretty much every day. There’s a bit of a learning curve with it, and it can seem somewhat unapproachable at times. This quick start primer covers a lot of the key concepts.
The CNCF has been busy preparing the next generation of cloud-native projects. They’re also preparing the next generation of cloud engineers with children’s books that teach Kubernetes concepts. Phippy and Friends is a great read if you’re five or just need someone to explain Kubernetes like you’re five.
We don’t know about you, but January flew by fairly quickly for all of us. Our quarterly meeting kicked off the month and had us celebrating our wins and looking forward to our organizational goals for 2020. Our Community Engagement Committee started planning for a STEM night at Algonkian Elementary at the end of February, as we begin to ramp up to bring our code club back into the classroom in the spring. We have a lot of exciting things happening over the next few months that we look forward to sharing with you.
You know what they say about all work and no play! A little beer, some good company (and of course poker) is how the Rhythmic team played in January!
We hope you solve some big problems and above all, have fun this month!
