A search on Google will turn up plenty of articles comparing MySQL to PostgreSQL. There are articles for beginners, exhaustive in-depth lists, and even an all-out fight video! So why does the internet need yet another MySQL vs. PostgreSQL article?
Well, we're going to take a different approach in this comparison. Many of the articles out there look at this topic based on things like use in websites or the availability of tools. We're instead going to look at things from the standpoint of a business application developer, both independent software vendors (ISVs) and enterprise IT.
Traditional software vendors who have been developing and deploying client-server applications on Windows desktop, face a dilemma.
On one hand, you have to maintain and support your existing customer base running on Windows desktop. On the other, you have to build new applications for the cloud because new customers prefer a cloud application.
We recently hosted a webinar that details how combining on-premise data and application APIs with customer-facing cloud apps offers you greater scalability and cost-savings.
So you want to build your first API. At some point in your pursuit, you've thought about how to make your API development easy. It can’t be too hard; everyone’s doing it. But as you travel down the road, you’re going to face some serious choices.
Most developers creating their first real API assume future-proofing will be their primary concern. Factoring in future upgrades and extensions is a real development issue, but it’s far from the only one. And it’s not even close to the most important at the outset.
As you begin building your API, you should be far more concerned with locking down security, choosing the correct protocol, and understanding how the API will support your application’s business model. Thankfully, here at Mertech, we can handle those things for you with these three ways.
APIs are a critical tool for building modern applications. But like all useful tools, you have to manage APIs properly in order to use them to greatest effect.
With that in mind, let’s take a look at the top seven challenges that arise when managing APIs. We’ll also discuss strategies for addressing each one in ways that ensure API scalability and resiliency.
What’s the point of an API? Ask most developers that question and they’ll tell you that APIs are useful because they connect different applications or services together.
But the importance of APIs extends even further. By embracing a concept known as API-driven development, you can leverage APIs not just as a tool for helping to build applications, but also as the very foundation of your entire development strategy.
This article explains what API-driven development means, why it’s important, how you can implement it and how to overcome common challenges associated with API-driven development.
In previous training sessions for Evolution (now Thriftly.io), we have covered the basics of developing an application: designing the user interface, creating an API and securing the application. All this is important, but developers ultimately need to know the best way to test and deploy their application to ensure they are releasing a bug-free and high-quality application to their market.
Focused on database support and feature parity, BTR2SQL Version 6 includes support for RDBMS versions of Microsoft SQL Server 2019, Oracle 19c, and PostgreSQL 12.
Flex2Crystal’s recent Version 3.2 release includes a series of exciting updates and optimizations, as well as important bug fixes to improve performance and user experience.