3/24/2023 0 Comments Dtsql license![]() When I worked on a dev team for proprietary software, it wasn't necessarily a guarentee that you would be working with developers that had the same skill level-This isn't to say that there aren't amazing engineers at Microsoft or Oracle because I'm sure there are. I can hardly recall any instance where they encountered a bug or a question they weren't able to address almost immediately. All of the guys I remember interacting with were phenomenal programmers. Even better, you can reach out to the developers directly via Github/StackOverflow etc.Īnother thing I noticed is that when I was in college, I was mostly in awe of the expertise of the professors in the CS department that contributed to open source projects. With open source, you can debug the issue by inspecting the source code yourself. I think it's often expected that you'll have to troubleshoot the issue yourself and find some kind of workaround. If you get in touch with a good engineer, the experience can be great but that's not always a guarantee. If you run into a bug in proprietary software, the only recourse you have is reaching out to the development team and waiting for them to investigate a ticket. For open source software, I occasionally find the support to be much, much better than a proprietary stack like Oracle or SQL Server. I've worked with open source and proprietary DB's since I graduated. I'm not sure the licensing model for Oracle, but at least for MSSQL that's roughly how it works. So you could have 40 servers with 4 cores each, you've effectively used 160 cores and paid for only 40 cores from the licensing standpoint. However, Microsoft doesn't care how many VMs you have. ![]() A quick run down of how clusters work is basically that you can share your cores across multiple virtual servers so let's say you have a 40 core ESX cluster and you pay 7k per core license on it. Yes the 7k per license for Enterprise seems like a lot, but many companies run virtual environments with licensing for the cluster itself. Licensing works differently for VMs (For SQL). You're gonna find a lot more DBAs and developers who know those products more than the open source ones most likely. That may be an extreme example, but it is something that is looked at when a company has to take account of it. Well, there goes any cost savings you had. This causes an outage of say 1 hour and the company makes let's say 20k an hour. Let's say now a new hire fucks up a code and it brings down the open source DB because of some bug or something. Let's say you don't pay the cost of a SQL server license for a 4 core server in order to save 14k and choose to go with an open source DB. For big companies where they rely on their server up time for money let's say an ecommerce site, using a robust product usually means you will unlikely take a hit due to the DB not being able to handle it. SQL and Oracle have been around for a long time and have had decades of refinement and development with very little to no bugs and when bugs do happen, they're usually addressed fairly quickly.This leads to.īetter up time, more money. This also falls in line with what kind of code your developers write. With open source products, there is no real hotline for you to call.Īpplication support, depending on the application, not everything can run on open source products or would require a ton of re architecture to work. ![]() Support via MS or Oracle if something is wrong. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |