Historically, most .NET applications have run on Windows. In fact, many people are still surprised to hear that some .NET applications can run on Linux. But that has actually been the case since 2004 when the open source project Mono 1.0 was released. Since 2014, .NET developers can also deploy some .NET applications to Linux using the .NET Core and ASP.NET Core frameworks. ASP.NET Core unites the previously separate ASP.NET MVC and Web API frameworks into a single programming model; it can run on both .NET Core and on the full .NET Framework.
Traditionally we have seen developers writing applications and ITOps managing and monitoring those applications in production. Though engineers on both sides don’t like to step on each others toes, one side is dependent on the other for running those applications in production with near zero downtime. Both have to coordinate with each other regarding capacity planning, easily comprehensible log messages and horizontal and vertical scalability of an application in production.
Editor's Note: Below is the video and transcript of a talk recently given by Josh Ellithorpe at DockerCon Seattle. Josh is a software architect at Apcera and has been working with containers for over three years. Been thinking about Moving Your Legacy Applications to Docker? Try it now with Apcera Community Edition
Alex Williams from The New Stack recently spent some time at Apcera HQ, taking a tour of our beautiful office (his words, not ours :)) as well as the new Apcera Platform Community Edition (CE). Alex sat down with Architect Josh Ellithorpe for a demo of the new, free product and its Developer Portal tutorials, API documentation and Community Forum.
It seems like only yesterday we were on stage at DockerCon Barcelona, basking in the glow of winning the littleBits MakerLab hackathon. Now DockerCon Seattle is just around the corner and we’re determined to make this our most memorable DockerCon yet. We’ll have awesome swag, a killer ecosystem talk and a local Apcerian tour guide-- so join us there from June 19-21 for an amazing ride!
If you've talked to someone from Apcera at any point, chances are you've heard us mention "policy" at some point—perhaps repeatedly. We tend to talk a great deal about it because it provides an excellent way to frame the conversation around what is allowed to run (and by whom), what resources can it consume, where it is running and what can that thing talk to/who can talk to it.
Editors note: This post was originally published on New Relic’s blog
The scene at the Georgia State Educational Technology Fair was total chaos. My fellow competitors were frantically setting up and testing their projects before showing them to the judges. I was setting up a compute cluster with a half-dozen microservices on a MacBook Pro and I had only 10 minutes to deploy and prepare. But man, that’s my idea of fun!
Today is an exciting day for Apcera and for all the developers out there who want a feature rich, secure and scalable container deployment and orchestration platform. After months of development the official release of Apcera Platform Community Edition (CE) is finally here.
IT organizations face a dilemma: focus on innovation (while introducing risk) or focus on security (while stifling innovation). It seems that most companies haven’t found a way to have their cake and eat it too.