Edge computing – with its ability to help unleash the potential of smart cities and autonomous vehicles, is something often thought to exist “around the corner” as opposed to an industry already in motion.

It’s been shown that if you follow a proven collection of practices for developing, designing, testing, implementing, and maintaining your software, you will produce a much higher quality product. Over the past few years, we have seen an increasing number of cases of attacks on the application layer. The Open Web Application Security Project, OWASP, estimates that around one-third of web applications contain security vulnerabilities.

This is a review of the last three years that we spent stabilizing Marathon. Marathon is the central workload scheduler in DC/OS. Most of the time when you launch an app or a service on DC/OS, it is Marathon that starts it on top of Apache Mesos. Mesos manages the compute and storage resources and Marathon orchestrates the workload. We sometimes dub it the “init.d of DC/OS”. Being such an integral part of DC/OS, we must ensure that it keeps functioning.

Technology has a way of circling around to the same ideas over time, but with different approaches that learn from previous iterations. Service Oriented Architecture (SOA) and Microservices Architecture (MSA) are such evolutionary approaches. Where lessons learned made sense, they were reused; and where painful lessons were learned, new methods and ideas were introduced.

The Internet has enabled a level of collaboration like never before in history. With just a few mouse clicks, you can see other people on the other side of the world and work with them remotely on whatever you want. Remote work is becoming new normal in many organizations. Managing teams remotely sometimes even in different time zones, with poor communication, monitoring becomes complex, and team misalignment is paramount.

Different IT organizations have different needs. The one-man shop might find the best success with open-source software, while enterprises often need something a little more. But occasionally you’ll see an enterprise using open-source or something designed for a small to medium-sized business. This can be a good thing in certain instances, though it’s not without risks. So, why might you want to use SMB or open-source gear in an enterprise setting, and when might it be a good thing?

When was the last time you had the chance to listen to some of the most beautiful concerts that nature can play for you? From simple chirps and tweets to complex bird songs composed into a sophisticated soundscape, you may wish you could decrypt and understand their daily conversation. “Hey, good morning, how are you today?”, you might hear in the early hours, sometimes so loudly that you are awakened from the chirping.

Your worst nightmare: a failure, a breakdown or any other inconvenience that can disrupt the smooth running of your daily activities that happens at the worst possible time. When you need your equipment, its reliability is absolutely paramount. In the absence of proper and functioning equipment, you’re not only wasting time, but you’re also jeopardizing employee productivity and the reputation of your service, all while seeing an increasement of operational cost.

As all Papertrail fans know, sending logs to Papertrail using syslog is quick and easy. Generating and transmitting syslog packets usually involves just 2 – 4 lines of code, and you can see your logs flowing into Papertrail in minutes. There are times, however, when you just can’t use syslog or install a remote_syslog2 daemon. This is where the new support for sending logs via HTTP comes in. And the best news is, it’s just as quick and easy to set up.

This is part of a series of articles discussing strategies to implement serverless architectural design patterns. We continue to follow this literature review. Although we use AWS serverless services to illustrate concepts, they can be applied in different cloud providers. In the previous article (Part 1) we covered the Aggregator and Data Lake patterns. In today’s article, we’ll continue in the Orchestration & Aggregation category covering the Fan-in/Fan-out and Queue-based load leveling.