Auxillery is a software integration platform for developers, technical teams, and organizations building across multiple programming languages, systems, and environments.
Instead of forcing teams to write repetitive APIs, serializers, and custom integration code every time systems need to communicate, Auxillery creates a shared transformation layer that allows software components to exchange data and call functionality more seamlessly across platforms.
Our mission is simple: make software more interoperable, reusable, and efficient, so teams can spend less time rebuilding what already exists and more time creating what comes next.
Fortran, Pascal, Python, Java, C, C++, C# and Bourne shell – each one has its own evangelists. But are they really that different?
You could interpret C and you could compile Bash (but we don’t)
From higher-level abstraction to inheritance to object-oriented and polymorphism, the designer of each language had their design goals and followers who adopted their technology
From HTTP to FTP to JDBC; each one serves a purpose. But are they really that different?
Use JDBC and DDL to create database tables. Use JDBC and DML to insert, read, update, and delete delete in those tables. Use FTP to send (put) files to, or receive (get) files from, a file server. Use HTTP to receive (GET) data from, or send (POST) data to a web server.
Do you begin to see more similarities than differences?
Have you heard of the saying that it’s 10x or 100x cheaper to fix a defect during development, than after it goes live?
What if instead of building a bigger more complicated more convoluted software development pipeline, we designed software expecting it to be changed, after go-live, and reduced the risk and impact of change to near-zero?
What better software could we build with 1/4 trillion lines of code?
What if we could reduce coding effort? What if we could re-use code – without having to clone it from git or copy-and-paste it into our workspace? What if we could recycle code – set it free from our workspace but keep it searchable and accessible so we could find it quickly for another project?
Image by Bernd Dittrich (unsplash.com)
There are so many different programming languages, which one do you pick to address the 1.8 trillion lines of code (in 20 years) problem? There are so many ways to represent (store, transport, access) data, ... (continue reading)
This is the simplest (most understated) demo of our software – The number of milliseconds past epoch January 1st, 1970 is: (ms) This simple (understated) demo shows how our RIP1 API uses client-side JavaScript in ... (continue reading)
As many as 1.8 trillion lines of code were written in the 20 years since the start of this millennium, according to a conservative estimate in an article written on Medium.com (1) That’s 93 billion ... (continue reading)