Using a low-code platform as the back-end for a single page application (SPA) is a nice combination — the SPA can be hosted anywhere, the API is quick and easy to develop, and they can evolve independently of each other e.g. if you need a native app just develop the UI and use the same API.

SOAP, being a mature technology, has an extensive and often differently interpreted standard set. This makes it an excellent tool for corporate users to manipulate data into their precise requirements and technology stack. However, for public consumption, this causes issues that sometimes are difficult or impossible to solve without changing code. A good example here is that SOAP is allowed to define the same type in some standard interpretations in different XSD files.

If you’re a SaaS company, it is impossible not to tackle the topic of integration. Whether you’re a small software business or a large, established tech enterprise with several SaaS products, every commercial conversation is highly likely to involve the question “Will I be able to sync data from your application with my CRM / ERP / Finance / Marketing” – you name it.

APIs or application programming interfaces make sure data is able to travel to and from specific destinations and sources with ease. Data isn’t the only thing that needs to travel safely, which is why APIs in the transportation industry are so popular for everything from booking an Uber to getting a shipment of goods delivered. APIs help websites, servers, and apps integrate efficiently and effectively by allowing different software endpoints to communicate with each other.

Photo by Tima Miroshnichenko from Pexels

With over 50,000 active organizations and 250 million workflows, CircleCI is one of the most popular networked CI platforms. When getting started with CI pipelines, teams typically want to ensure that code will compile, pass unit tests, and build a container image. After catching these low hanging fruit of syntax errors, engineering teams need to dig much further to find business logic and scalability errors.

Are you someone who already has a legacy system in place and wants to migrate to a modern authentication system with Identity and Access Management (IAM) features? The first thing you need to consider is how you can use the existing legacy user store with this new system. Keep in mind that if the legacy user store uses an old security mechanism to store your data, we would recommend that you migrate to the WSO2 JDBC user store format or Active Directory (AD).

Jason Cumberland, CPO and co-founder of API and data monetization platform HyperCurrent, contributed to this post. In our last article on how to get started with API monetization, we laid out how to build your API monetization strategy and avoid common pitfalls that occur when trying to get to your first minimum viable product release.

API integrations are foundational to the innovation and agility companies need to remain competitive. Using APIs lets companies connect systems to build new capabilities to extend their services and provide enhanced customer experiences. This guide discusses API integrations and shows you how to define an API integration to start building your API ecosystem.