I previously made a blog post on how to manually setup Sitecore running in a Docker container. I would like to take it one more step and build a Docker image using an automated install of Sitecore during the build process. We can then build Sitecore development enviornments on demand using our Docker Sitecore image.
Since the initial launch of the OpenStack Innovation Center back in July of 2015, much work has been done. Wanted to take a moment to share the current status and some details about its next phases. If you are unfamiliar with OSIC, let me start off with some very quick background information.
MongoDB has made some noticeable improvements with the 3.0 release and new engine, WiredTiger. This post shows how those improvements in MongoDB translate into real performance gains for your application.
In my previous blog post on running Sitecore in a Docker container, I used Azure SQL to host my Sitecore databases. Wanting a clean enviornment each time I develop, I needed a quick way to provision to Azure. With that requirement, I wrote a PowerShell script that makes this task repeatable for development and testing.
At SUGCON 2015, Rackspace and Hedgehog presented about how using Docker will shape the way we work with Sitecore, an ASP.Net web content management system. With the release of Windows Server 2016 Technical Preview 4, we are now able to run Sitecore in a Docker container.
I have spent the majority of my career as a Java developer. As a result, I learned to be more productive using an IDE instead of an editor like Vi. Even though Vi is still my editor of choice when I’m in a Linux shell, I don’t believe it’s practical when managing large Java projects.
AEM 6.1 With MongoDB 3.0 and WiredTiger
Adobe, with the release of AEM 6.1, [officially supports][adobe1] MongoDB 3.0 and its plugabble engine WiredTiger. This post will take you through installing and configuring AEM 6.1 and MongoDB to take advatange of [performance improvements in MongoDB 3.0.][or1]
Virtual Machine Scale Sets, which was recently released in preview from Microsoft, lets you manage a set of virtual machines as one.
Over the last couple of years, we've seen OpenStack deployments shift from a public cloud model, where no one is trusted, to a private cloud model, where collaboration and shared resources between projects is required. As enterprises adopt OpenStack and integrate it into their infrastructure, new use cases continue to multiply, and existing limitations in APIs and data models have been brought to the forefront. One of the more exciting features to come out of Neutron development in the Liberty cycle that addresses a shortcoming is a framework for Role Based Access Control (RBAC).
In the good old days the measure of a programmer was efficiency - how much functionality could be packed into how much space. Languages like C keep code close to the machine and require close attention to, and strong understanding of, machine operation for performance and code execution.
Much like with the catapult, new methods have come along for launching higher-delivery projectiles at high speeds, but, when it comes to hurling a VW beetle the length of a football field, sometimes the old ways are still the best. The importance of efficiency in code has been maligned, and largely obfuscated, by modern delivery mechanisms; however, its effect remains critical to the performance of complex large-scale applications.