Is the first thing that comes to mind a technical community (data, programming language, visualization tools, etc.) or something else? Whatever community that was, how did you feel after first stepping through the proverbial door?ĭid you have a crowd of people ready to cheer you on, eager to see you succeed, and ready to support you? When was the last time you had to join a new community? And I can say, without a doubt, that I'm not the only one looking for the same thing. IBIZ CYBERTECH PVT LTD PROFESSIONALIn fact, since coming back into the PostgreSQL community almost 4 years ago, I've continued to look for ways to foster a community and learning modeled after what I knew and experienced through SQL Server and the Professional Association of SQL Server (PASS) community. And while PostgreSQL has occupied the second largest (and longest) portion of my database landscape, I really came of age as a database professional within the SQL Server community. For nearly 15 of the last 21 years, I was primarily a Microsoft data platform user. So, why do I care? Well, if you were to put my 20+ years of database experience into a word cloud of sorts, SQL Server would occupy the largest portion of space. And regardless of how we feel about the new demands, this will put on this community, it's a group of people that still want to do their job well and contribute back to the community. IBIZ CYBERTECH PVT LTD HOW TOI believe this means that over the next 2-4 years, the community will grow from a base of users that have a lot of database experience but have little footing for how to approach a similar, but different, database. IBIZ CYBERTECH PVT LTD CODEWhether the necessary patches are included in the core PostgreSQL code or not, AWS Aurora, at least, will still offer this functionality as a service. The proverbial cat is already out of the bag. Regardless of how we feel about this new turn of events or the potential onslaught of new support needs by users of SQL Server, there's not much we can do about it. is easy to enhance through extensibility.is the fastest growing, relational database engine on the planet.While I can posit many reasons why Amazon AWS chose to go directly after SQL Server for this transparent compatibility tool, the reasons to use PostgreSQL as the solution to the problem is obvious to the PostgreSQL community. While the three other engines have had some steady decline over the same period, SQL Server seems to have the biggest drop off compared to Oracle and MySQL.Only PostgreSQL has seen consistent increases in popularity and engagement over the 9 years of tracking.When I zoomed in on the four "major" relational database engines, utilizing the last 9 years of data, two things jumped out at me. Although the website doesn't disclose the specific method for determining database engine rank, we know that social engagement and search engine trends play a role in the rankings. I decided to look at to see if the engagement metrics that they track would shed any light on it. It also got me thinking - why SQL Server? However, I didn't leave that call any less concerned about the struggles my SQL Server friends will have as their management teams mandate switching to PostgreSQL using Babelfish. It was interesting, and kind of exciting to see what worked and what didn't. Not long after the release was announced, I had the opportunity to participate in a video call with some members of the European PostgreSQL community for a first look at Babelfish in real life. But in October 2021, Babelfish was finally released for public access and preview at. Until recently, however, all we knew about Babelfish was based on Amazon published content. While these tools have proven to be hugely useful to many developers, nearly every DBA has first-hand war stories that demonstrate the challenge that automated query generation can impose on a complex system. In fact, my first thought was that Babelfish is just an oversized Object-Relational Mapping (ORM) framework that wasn't tied to any specific development language. I'm not sure that most people in either community really gave it that much notice a year ago. To be honest, as someone that's spent a significant part of my career using both SQL Server and PostgreSQL, this wasn't actually a very “exciting” development. Twitter: December 1, 2020, at its annual re:Invent conference, Amazon AWS announced Babelfish - an open source PostgreSQL translation layer that allows SQL Server applications to work natively, and transparently, with PostgreSQL. The future of community in light of Babelfish
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |