Systems | Development | Analytics | API | Testing

Development

What is Clojure? Functional Programming for the Java Ecosystem

Most programming languages are built on procedural programming, but there is this niche of dialects built for “functional programming,” where code classes are dynamically created based on the rules in the functions you write. If you could put languages on a scale of most procedural to most functional, you’d find Clojure sitting at the edge of the latter. What is Clojure? Who uses Clojure? What’s the best Clojure use case?

Appian Academy: Take Control of Your Low-Code Destiny

Bring your people, processes, and data together seamlessly and rapidly launch mobile-ready applications with the Appian Low-Code Platform. And with Appian Academy, you’ll feel empowered to get the most out of your investment. The Appian Academy helps get technical and non-technical users up to speed quickly, incorporate Appian into business operations, and recognize future opportunities with the right low-code mindset.

How to Plug an Existing User Store into WSO2 Identity Server?

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).

API monetization: Technical best practices

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.

Using Scientist to Refactor Critical Ruby on Rails Code

Ask any software engineer to review key portions of production code, and inevitably, they will point out three things that need to be refactored. So why does so much bad, brittle, or misunderstood code remain running in production? The answer is simple: engineers are afraid to touch it. Refactoring tasks get identified and added to the backlog, but rarely make it into the current sprint. There are numerous reasons for this.