Public cloud services -- Amazon AWS, Google Cloud, IBM Cloud, Microsoft Azure, offer the simplicity and convenience of CapEx-less buy-as-you-go/as-you-need compute and storage. However, in return, you have to accept some limitations, notably, sacrificing some degrees of control.
What a crazy few weeks it has been. Marriott started it off with the announcement that over 500M records had been stolen from its database and worse - they know the attackers were in their systems for up to 4 years which was during an acquisition and even after the prior year when they found a RAT (remote access trojan).
Supporting your organization's computing requirements "at the edge" -- away from the corporate office or data center -- has always faced challenges. "Big data" generated by IoT devices and other sources can often overwhelm even broadband connections to distant cloud centers -- and many "edge sites" have little or no connectivity.
Are unikernels unfit for production? Are unikernels completely undebuggable? There are so many unsubstantiated claims being made about ‘debugging unikernels’ that I feel I need to address some of them.
Many people have heard of the security advantages of unikernels. These commonly get boiled down to "it’s a smaller attack surface." Unfortunately, that does little justice to the true security implications of running your software as unikernels. So let’s revisit what the unikernel four point security model actually is.