Dev Discuss | Why We Built Our Own Functions as a Service

Dev discussion with Rocky Madden, avid functional programming, computational science, and high-scalability engineer. Lover of the sciences. Core contributor on the Cloud Elements Platform team. Background: The Cloud Elements Platform is transitioning towards more microservices, including serverless microservices, in its architecture.

One of the key pieces in extending our platform is the use of a Functions-as-a-Service platform. Functions compute and execute code triggered by events, on a regular schedule, or in an ad-hoc manner. However, current commercial and open source services have issues with performance, cost, and most importantly lack features for our use cases, so we built our own Functions as a Service (FaaS) platform. https://goo.gl/c99wws #DataIntegration #ML

5 Reasons You Should Use OpenAPI/Swagger for Your APIs

If you develop software today, chances are you are developing Web APIs as well. But while you might not be a company like Twilio that is running a huge public API program, there is still a high chance you are building APIs for some selected partners or even just for internal use. For example, to connect your native mobile applications to your backend.

In all these cases, your software development lifecycle and server operations involve APIs. If you are still not using a definition language for machine-readable API specifications, such as OpenAPI (formerly known as Swagger), you should definitely consider doing so. After all, APIs are languages for machines to talk to each other. So it makes sense that their process and documentation is written in a way that machines can understand and participate in as well. https://goo.gl/vopC9t #DataIntegration #ML