Vern  Greenholt

Vern Greenholt

1594793280

Open Source Databases in the Age of the DBaaS – The New Stack

While I love open source for the freedoms it provides, this was not the reason why I started working with and developing free and open source software. Back at the beginning of my career in 1999, I was a student in Russia starting my first startup and I needed a way to do it in the most cost-effective way possible. Servers were already commoditized by this time and they could be acquired relatively inexpensively — especially if you were frugal enough to obtain three-year-old hardware — but software was not cheap. If you wanted to purchase it legally you would need to pay a lot of greenbacks for Microsoft stack or Oracle database. This being Russia in the late 1990s, you also could buy a pirate version for a couple of bucks, but I wasn’t interested in doing that.

In truth, my first startup only got off the ground because of open source software. Linux, Apache, PHP, MySQL were all in their infancy and not nearly as powerful — and easy to use — as most open source technologies today, but they enabled innovation to flourish which would not have happened otherwise.

Now, more than 20 years later the world has changed and resourceful founders around the world are unlikely to be racking second-hand servers, but would rather start their technology company using cloud services.

However, the same logic applies: if you’re using commodity cloud technology you will likely have many low-cost options available compared to choosing a solution that is only available from one vendor. For example, nowadays if you’re looking for inexpensive Amazon Web Services EC2 alternatives, there are providers such as Linode or Hetzner or cheaper S3 alternatives, and there’s Backblaze which offers more cost-effective storage. Just the fact that you have plausible alternatives means vendors are forced to be more reserved in their pricing model.

If you are using highly differentiated cloud services, which are far from commoditized, you don’t have the same freedom of choice, so you are forced to accept the pricing and service quality of the vendor who offers the solution. In other words, you’re stuck with vendor lock-in.

If we look at databases, the preferred way to consume databases by many is through DBaaS (Database-as-a-Service), rather than installing and managing database software manually. If this is the approach you have embraced, your choices in the cloud will vary, although none of them will offer the same portability that you get from a solution built on open source software and commoditized services:

#data #open source #contributed #data analysis

What is GEEK

Buddha Community

Open Source Databases in the Age of the DBaaS – The New Stack
Ray  Patel

Ray Patel

1623348300

Top 8 Java Open Source Projects You Should Get Your Hands-on [2021]

Learning about Java is no easy feat. It’s a prevalent and in-demand programming language with applications in numerous sectors. We all know that if you want to learn a new skill, the best way to do so is through using it. That’s why we recommend working on projects.

So if you’re a Java student, then you’ve come to the right place as this article will help you learn about the most popular Java open source projects. This way, you’d have a firm grasp of industry trends and the programming language’s applications.

However, before we discuss its various projects, it’s crucial to examine the place where you can get those projects – GitHub. Let’s begin.

#full stack development #java open source projects #java projects #open source projects #top 8 java open source projects #java open source projects

Tyrique  Littel

Tyrique Littel

1598461200

An Open-Source Book About the Open Source World

Open source today is a word that often include a lot of things, such as open knowledge (Wikimedia projects), open hardware (Arduino, Raspberry Pi), open formats (ODT/ODS/ODP) and so on.

It is a world of opportunities that can be difficult for newcomers but also for intermediates. This article will help you discover how to approach specific roles, activities or projects/communities in the best way.

Everything Started with “Coaching for OpenSource Communities 2.0”

I decided to write a book in my personal style about my experience in the last 7 to 8 years in open source. I was surprised when I reached 100 pages about various different topics.

My idea was to write something that I would like to read, so nothing that is boring or complicated, but full of real facts.

The second goal was to include my experience but also my philosophy on contributing and how I contribute daily.

Thirdly, I wanted to give a lot of hints and resources and an overall view of this open source world.

Basically, I wanted to write something different from self-help or coaching books that includes just a list of suggestions and best practices. Instead, I take real examples from real life about the OSS world.

As a contributor and developer, I prefer to have real cases to study, because best practices are useful, but we need to learn from others and this world is full of good and bad cases to discover.

In 2019, I started writing a book after Fosdem 2019 and after 2 years inside the Mozilla Reps Council. In that Fosdem edition, I had a talk “Coaching for Open Source Communities 2.0” and after the feedback at the conference and my thoughts in various roles, activities, and projects, it was time to write something.

At the end it wasn’t a manual but a book that included my experience, learnings, best practices and so on in Localization, Development, Project Maintainer, Sysadmin, Community Management, Mentor, Speaker and so on. It contains the following sections:

  • Biography - This choice isn’t for self promotion but just to understand my point of view and my story that can be inspiring for others
  • Philosophy - Not the usual description of Open Source or the 4 freedoms, but just what Open Source means and how you can help
  • How to live inside the Open Source - A discovery about communications and tools, understanding the various kind of people and the best way to talk with your community
  • How to choose a project - Starting with some questions to yourself and how to involve more people in your project
  • The activity - Open Source is based on tasks that can be divided in 2 levels: Support, Testing, Marketing, Development etc
  • How to use your time - We are busy, we have a life, a job and a family but Open Source can be time-consuming
  • Why document is important - How writing documentation can be healthy for your community and the project’s future and brand

There are also three appendices that are manuals which I wrote throughout the years and gathered and improved for this book. They are about: community management, public speaking, and mentoring.

The book ends with my point of view about the future and what we have to do to change opinions about those topics.

I wrote this book and published in October 2019, but it was only possible with the help of reviews and localizers that improved and contributed. Yes, because this book is open source and free for everyone.

I picked the GPL license because this license changed the world and my life in the best way. Using this license is just a tribute. This decision usually is not clear because after all this is a book and there are better licenses like Creative Commons.

#open-source #contributing-to-open-source #programming #software-development #development #coding #books #open-source-software

Hertha  Mayer

Hertha Mayer

1595334123

Authentication In MEAN Stack - A Quick Guide

I consider myself an active StackOverflow user, despite my activity tends to vary depending on my daily workload. I enjoy answering questions with angular tag and I always try to create some working example to prove correctness of my answers.

To create angular demo I usually use either plunker or stackblitz or even jsfiddle. I like all of them but when I run into some errors I want to have a little bit more usable tool to undestand what’s going on.

Many people who ask questions on stackoverflow don’t want to isolate the problem and prepare minimal reproduction so they usually post all code to their questions on SO. They also tend to be not accurate and make a lot of mistakes in template syntax. To not waste a lot of time investigating where the error comes from I tried to create a tool that will help me to quickly find what causes the problem.

Angular demo runner
Online angular editor for building demo.
ng-run.com
<>

Let me show what I mean…

Template parser errors#

There are template parser errors that can be easy catched by stackblitz

It gives me some information but I want the error to be highlighted

#mean stack #angular 6 passport authentication #authentication in mean stack #full stack authentication #mean stack example application #mean stack login and registration angular 8 #mean stack login and registration angular 9 #mean stack tutorial #mean stack tutorial 2019 #passport.js

Houston  Sipes

Houston Sipes

1600992000

Did Google Open Sourcing Kubernetes Backfired?

Over the last few years, Kubernetes have become the de-facto standard for container orchestration and has also won the race against Docker for being the most loved platforms among developers. Released in 2014, Kubernetes has come a long way with currently being used across the entire cloudscape platforms. In fact, recent reports state that out of 109 tools to manage containers, 89% of them are leveraging Kubernetes versions.

Although inspired by Borg, Kubernetes, is an open-source project by Google, and has been donated to a vendor-neutral firm — The Cloud Native Computing Foundation. This could be attributed to Google’s vision of creating a platform that can be used by every firm of the world, including the large tech companies and can host multiple cloud platforms and data centres. The entire reason for handing over the control to CNCF is to develop the platform in the best interest of its users without vendor lock-in.

#opinions #google open source #google open source tools #google opening kubernetes #kubernetes #kubernetes platform #kubernetes tools #open source kubernetes backfired

Vern  Greenholt

Vern Greenholt

1594793280

Open Source Databases in the Age of the DBaaS – The New Stack

While I love open source for the freedoms it provides, this was not the reason why I started working with and developing free and open source software. Back at the beginning of my career in 1999, I was a student in Russia starting my first startup and I needed a way to do it in the most cost-effective way possible. Servers were already commoditized by this time and they could be acquired relatively inexpensively — especially if you were frugal enough to obtain three-year-old hardware — but software was not cheap. If you wanted to purchase it legally you would need to pay a lot of greenbacks for Microsoft stack or Oracle database. This being Russia in the late 1990s, you also could buy a pirate version for a couple of bucks, but I wasn’t interested in doing that.

In truth, my first startup only got off the ground because of open source software. Linux, Apache, PHP, MySQL were all in their infancy and not nearly as powerful — and easy to use — as most open source technologies today, but they enabled innovation to flourish which would not have happened otherwise.

Now, more than 20 years later the world has changed and resourceful founders around the world are unlikely to be racking second-hand servers, but would rather start their technology company using cloud services.

However, the same logic applies: if you’re using commodity cloud technology you will likely have many low-cost options available compared to choosing a solution that is only available from one vendor. For example, nowadays if you’re looking for inexpensive Amazon Web Services EC2 alternatives, there are providers such as Linode or Hetzner or cheaper S3 alternatives, and there’s Backblaze which offers more cost-effective storage. Just the fact that you have plausible alternatives means vendors are forced to be more reserved in their pricing model.

If you are using highly differentiated cloud services, which are far from commoditized, you don’t have the same freedom of choice, so you are forced to accept the pricing and service quality of the vendor who offers the solution. In other words, you’re stuck with vendor lock-in.

If we look at databases, the preferred way to consume databases by many is through DBaaS (Database-as-a-Service), rather than installing and managing database software manually. If this is the approach you have embraced, your choices in the cloud will vary, although none of them will offer the same portability that you get from a solution built on open source software and commoditized services:

#data #open source #contributed #data analysis