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.
Flex2SQL Version 16 adds support for new RDBMS releases from Microsoft, Oracle, MariaDB, and PostgreSQL. In addition, this new release includes a series of exciting updates, important bug fixes, and significant optimizations, like extended support for the cloud and failover clustering.
This month we released the latest version of Thriftly. Featuring an array of enhanced services and error fixes, v2.3 is more versatile and dependable than ever before.
Pembroke Pines, FL – Mertech Data Systems, a global provider of application modernization tools and services, is pleased to announce that it has earned Microsoft Gold competency status in Cloud Platform.
The process of modernizing legacy applications into a service-oriented architecture is a long one. For many, the logic that is required for new, modern systems already exists in the form of code that has already been written, fully tested, and used for multiple years in the form of thick-client Windows applications. The process of starting over, defining cloud APIs and re-implementing the logic and data tier can prove to be time-consuming and error-prone.
If you’re a developer who works with APIs, you’ve probably spent a lot of time discussing or debating REST vs. SOAP vs. RPC or other API protocols. 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.
Migrating your applications from a monolith architecture (in which all application components are deployed as a single piece of code) to a cloud-native model could be just the thing that your business needs to take things to the next level. There are many advantages to such a migration.
But like most things in life worth doing, making the transition to cloud-native can be tough. There are many pitfalls you could encounter that could make the migration not worth the effort.
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.
