muuntaja
paos
muuntaja | paos | |
---|---|---|
1 | 1 | |
431 | 90 | |
0.5% | - | |
7.1 | 0.0 | |
about 2 months ago | over 1 year ago | |
Clojure | Clojure | |
Eclipse Public License 2.0 | Eclipse Public License 1.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
muuntaja
paos
-
Clojure needs a Rails, but not for the reason you think
Just library-driven-development.
I used the paos library (https://github.com/xapix-io/paos). Mainly followed the quick start examples on the github page. Fetched the wsdl from the API provider, pulled out the SOAP envelope which translates into a Clojure map. The API provider has a bunch of soap services that each provide a large number of keys in the envelope but many keys in many services aren't capable of actually doing anything server-side. This was . . . documented poorly.
We have dev and test environments for this specific API provider so I hacked around and made calls until I had everything working.
This is a perfect example of the kind of one-off stuff I often use Clojure for. Quick prototypes to get work done. There are many groups in my larger organization and a common experience for me is to have groups tell you "X can't be done because Y." In this case, a vendor was charging 5 figure fees per data migration effort for each planned migration. The plan was to roll out by group and there are many groups. My immediate question was "can't we do this with the API and save these fees?" The answer was "no, not possible." About three days later I had a working version for this admittedly simple use case, demo'd it, rolled it into production. The cost savings will be in the low six figures. Of course, once it was working the original internal group came back to re-implement the project in another language because "bus factor" but tbh there is lots of weirdness in my larger employer organization about who gets to do what. Once I had shown we could do it relatively easily, teams come out of the woodwork to grab it so that they can add the cost savings to their yearly brag results.
I could write for days about this type of thing . . .
What are some alternatives?
reitit - A fast data-driven routing library for Clojure/Script
bidi - Bidirectional URI routing
clojure-news-feed - evaluating various technologies by implementing a news feed micro-service
luminus-template - a template project for the Luminus framework
overarch - Overarch provides a data model for the holistic description of a software system, opening multiple use cases on the model data. Supports C4 and UML diagram generation with PlantUML.
edge - A Clojure application foundation from JUXT
stripe-python - Python library for the Stripe API.
ripley - Server rendered UIs over WebSockets
slack-ruby-client - A Ruby and command-line client for the Slack Web, Real Time Messaging and Event APIs.
yada - A powerful Clojure web library, full HTTP, full async - see https://juxt.pro/yada/index.html
component - Managed lifecycle of stateful objects in Clojure