If you’re a developer who supports multiple API protocols, you’ve probably spent a lot of time discussing or debating REST vs. SOAP vs. RPC or other APIs. Depending on your point of view, you might think that one API protocol is better than another, and seek to use that protocol whenever possible.
In this, webinar, we cover API security: encryption, authentication, and authorization. We will be covering how secure API design starts with you and how you should be thinking like a villain when setting up security.
Designing APIs is easy. Designing good APIs, however, is not.
That’s because when it comes to API design, there are a lot of considerations that must be weighed outside of core functionality. From naming conventions to version management, the details of an API’s design can mean the difference between success and failure.
Like everything else that powers software infrastructure, APIs must be secured. That you know.
But do you understand how to go about securing an API? The API security process starts (or should start, at least) with API design. If you wait until you’ve already created your API to think about security, you’re fighting an uphill battle, because you’ll be trying to plug security holes that you could have prevented in the first place.
PHP has become one of the most popular web development languages used today. Sometimes mocked for its inconsistency and accidental rise to prominence, PHP’s ease of use still makes it perfectly suited for simple web development.
But what if you need to connect a more complex application or data source with your PHP app? For that, you’ll want to lean on APIs. In this post, you’ll learn how to connect a JSON-RPC API, created in Thriftly, to a PHP-based application, making it easy to access complex data in simple web apps.
For the past couple of years, microservices have been a hot topic of conversation in the field of information technology. The hype around microservices is that they make everything better, and as an engineer who works on an application, I’m an enthusiastic promoter of the philosophy.
When properly implemented, a microservices architecture offers many benefits. However, this approach isn’t right for every organization or application. In this article, we’re going to look at microservices in more depth, and discuss how you can use an API-based approach to implement and manage them. We’ll also discuss the advantages of this approach, and some of the reasons why you should or shouldn’t consider microservices.
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.