• MariaDB opens US headquarters in California

  MariaDB Corporation, the database company born as a result of forking the well-known open-source MySQL database...

• ScyllaDB takes on Amazon with new DynamoDB migration tool

  There are a lot of open-source databases out there, and ScyllaDB, a NoSQL variety, is looking to differentiate itself by attracting none other than Amazon users. Today, it announced a DynamoDB migration tool to help Amazon customers move to its product.

• ScyllaDB Announces Alternator, an Open Source Amazon DynamoDB-Compatible API

  ScyllaDB today announced the Alternator project, open-source software that will enable application- and API-level compatibility between Scylla and Amazon’s NoSQL cloud database, Amazon DynamoDB. Scylla’s DynamoDB-compatible API will be available for use with Scylla Open Source, supporting the majority of DynamoDB use cases and features.

• ScyllaDB Secures $25 Million to Open Source Amazon DynamoDB-compatible API

  Fast-growing NoSQL database company raises funds to extend operations and bring new deployment flexibility to users of Amazon DynamoDB.

• ScyllaDB Announces Alternator, an Open Source Amazon DynamoDB-Compatible API

  ScyllaDB today announced the Alternator project, open-source software that will enable application- and API-level compatibility between Scylla and Amazon’s NoSQL cloud database, Amazon DynamoDB. Scylla’s DynamoDB-compatible API will be available for use with Scylla Open Source, supporting the majority of DynamoDB use cases and features.

• ScyllaDB powers up Alternator: an open Amazon DynamoDB API

  Companies normally keep things pretty quiet in the run up to their annual user conferences, so they can pepper the press with a bag of announcements designed to show how much market momentum and traction that have going.

  Not so with ScyllaDB, the company has been dropping updates in advance of its Scylla Summit event in what is perhaps an unusually vocal kind of way.

  [...]

  Scylla itself is a real-time big data database that is fully compatible with Apache Cassandra and is known for its ‘shared-nothing’ approach (a distributed-computing architecture in which each update request is satisfied by a single node –processor/memory/storage unit to increase throughput and storage capacity.

• Percona Announces Full Conference Schedule for Percona Live Open Source Database Conference Europe 2019

  The Percona Live Open Source Database Conference Europe 2019 is the premier open source database event. Percona Live conferences provide the open source database community with an opportunity to discover and discuss the latest open source trends, technologies and innovations. The conference includes the best and brightest innovators and influencers in the open source database industry.

• Thwarting Digital Ad Fraud at Scale: An Open Source Experiment with Anomaly Detection

  Our experiment assembles Kafka, Cassandra, and our anomaly detection application in a Lambda architecture, in which Kafka and our streaming data pipeline are the speed layer, and Cassandra acts as the batch and serving layer. In this configuration, Kafka makes it possible to ingest streaming digital ad data in a fast and scalable manner, while taking a “store and forward” approach so that Kafka can serve as a buffer to protect the Cassandra database from being overwhelmed by major data surges. Cassandra’s strength is in storing high-velocity streams of ad metric data in its linearly scalable, write-optimized database. In order to handle automation for provisioning, deploying, and scaling the application, the anomaly detection experiment relies on Kubernetes on AWS EKS.

• Develop with Flask and Python 3 in a container on Red Hat Enterprise Linux

  In my previous article, Run Red Hat Enterprise Linux 8 in a container on RHEL 7, I showed how to start developing with the latest versions of languages, databases, and web servers available with Red Hat Enterprise Linux 8 even if you are still running RHEL 7. In this article, I?ll build on that base to show how to get started with the Flask microframework using the current RHEL 8 application stream version of Python 3.

  From my perspective, using Red Hat Enterprise Linux 8 application streams in containers is preferable to using software collections on RHEL 7. While you need to get comfortable with containers, all of the software installs in the locations you?d expect. There is no need to use scl commands to manage the selected software versions. Instead, each container gets an isolated user space. You don?t have to worry about conflicting versions.

  In this article, you?ll create a Red Hat Enterprise Linux 8 Django container with Buildah and run it with Podman. The code will be stored on your local machine and mapped into the container when it runs. You?ll be able to edit the code on your local machine as you would any other application. Since it is mapped via a volume mount, the changes you make to the code will be immediately visible from the container, which is convenient for dynamic languages that don?t need to be compiled. While this approach isn?t the way to do things for production, you get the same development inner loop as you?d have when developing locally without containers. The article also shows how to use Buildah to build a production image with your completed application.

• IBM brings Cloud Foundry and Red Hat OpenShift together

  At the Cloud Foundry Summit in The Hague, IBM today showcased its Cloud Foundry Enterprise Environment on Red Hat?s OpenShift container platform.

  For the longest time, the open-source Cloud Foundry Platform-as-a-Service ecosystem and Red Hat?s Kubernetes-centric OpenShift were mostly seen as competitors, with both tools vying for enterprise customers who want to modernize their application development and delivery platforms. But a lot of things have changed in recent times. On the technical side, Cloud Foundry started adopting Kubernetes as an option for application deployments and as a way of containerizing and running Cloud Foundry itself.

• SAN vs. NAS: Comparing two approaches to data storage

  For a new sysadmin, storage can be one of the more confusing aspects of infrastructure. This confusion can be caused by lack of exposure to new or different technologies, often because storage needs may be managed by another team. Without a specific interest in storage, an admin might find one’s self with a number of misconceptions, questions, or concerns about how or why to implement different solutions.

  When discussing enterprise storage, two concepts are at the core of most conversations: storage area networks (SAN) and network-attached storage (NAS). Both options provide storage to clients across a network, which offers the huge benefit of removing individual servers as single points of failure. Using one of these options also reduces the cost of individual clients, as there is no longer a need to have large amounts of local storage.

• Introduction to virtio-networking and vhost-net

  In this post we have scratched the surface of the virtio-networking ecosystem, introducing you to the basic building blocks of virtualization and networking used by virtio-networking. We have briefly covered the virtio spec and the vhost protocol, reviewed the frontend and backend architecture used for implementing the virtio interface and have taken you through the vhost-net/virtio-net architecture of vhost-net (host kernel) communicating with virtio-net (guest kernel).

  A fundamental challenge we had when trying to explain things was the historical overloading of terms. As one example, virtio-net refers both to the virtio networking device implementation in the virtio specification and also to the guest kernel front end described in the vhost-net/virtio-net architecture. We attempted to address this by explaining the context of terms and using virtio-net to only describe the guest kernel frontend.

  As will be explained in later posts, there are other implementations for the virtio spec networking device based on using DPDK and different hardware offloading techniques which are all under the umbrella of the virtio-networking.

  The next two posts are intended to provide a deeper understanding of the vhost-net/virtio-net architecture. One post will be intended for architects providing a technical deep dive into the vhost-net/virtio-net and explaining how in practice the data plane and control planes are implemented. The other post intended for developers will be a hands on session including Ansible scripts to enable experimenting with the vhost-net/virtio-net architecture.

  If you prefer high level overviews we recommend you keep an eye out for the virtio-networking and DPDK introductions, to be published in the upcoming weeks.

• Intel Issues Second Release Of Its Rust-Written Cloud-Hypervisor For Modern Linux VMs

  Intel's open-source crew has released version 0.2 of its primarily Rust-developed Cloud Hypervisor and associated firmware also in Rust.

  The Intel Cloud Hypervisor is their experimental VMM running atop KVM designed for modern Linux distributions and VirtIO para-virtualized devices without any legacy device support.

• Announcing SUSE CaaS Platform 4

  SUSE CaaS Platform 4 raises the bar for robust Kubernetes platform operations with enhancements that expand platform scalability options, strengthen application security, and make it easier to keep pace with technology advancements. Integrating the latest releases of Kubernetes and SUSE Linux Enterprise, SUSE CaaS Platform 4 continues to provide industry leading application delivery capabilities as an enterprise-ready solution.

• A new era in Cloud Native Application Delivery is here

• 3 Infrastructure Compliance Best Practices for DevOps

  For most IT organizations, the need for compliance goes without saying. Internal corporate policies and external regulations like HIPAA and Sarbanes Oxley require compliance. Businesses in heavily regulated industries like healthcare, financial services, and public service are among those with the greatest need for strong compliance programs.

Within this segment, the strongest sound is Matrix, an interesting open and decentralized standard for communication designed for interoperability in a similar way to the interoperability existing in the e-mail segment, Enabling real-time communication between users regardless of the customers or servers they use.

Currently, the standard and all its development is maintained by Matrix.org Foundation, a non-profit organization based in the United Kingdom.

Matrix has been developed with privacy and security in mind, taking into account the federation between servers, so that a user can communicate in any existing room securely, with end-to-end encryption, regardless of the server Where you have registered your account, and using any client of your choice.

There are also gateways to participate through messaging programs such as Telegram, discord or Slack, among others.

Matrix allows communication between users basically via text chat, audio calls and video calls, along with other possibilities.

In addition, it aims to surpass the relative success achieved by the standards SIP, XMPP and RCS trying to circumvent the obstacles that have prevented that the standards now mentioned have not been able to go to more.

Among the customers, the best known is Riot, also open-source. Those who do not want to create their own self-hosted Matrix servers, have the possibility to hire some of Modular.im’s plans to create their servers with a few clicks away, depending on their needs.

Also: Sparky Linux: Riot