Compilation target support from Go and other languages makes it really easy to provide your library to websites - which we use for demos. It's quick to compile Go code into WASM and show folks quickly what your library offers.
Plus the demo's computation happens client side so no data is sent to a server.
We can offer our full payment parsing libraries to the web as developer tools without any code changes. I don't have to care about the details of WASM because it "just works".
Moov powers infinite payment use cases with full data transparency. However you decide to orchestrate the motion of money: pay by bank, pay by card, disburse to a Moov wallet or linked bank account with same-day ACH or RTP®, or spend with an issued card—we’ve got you covered.
"Moov has become an integral part of our strategy at Jack Henry. Their platform’s developer-first approach allows us to innovate quickly and stay ahead of industry demands. Moov’s world-class engineering and design team has deep experience navigating complex payment infrastructure, which helps us win because we’re able to focus on building exceptional customer experiences." – Ben Metz, CTO, Jack Henry
Our technology stack includes: Go, PostgreSQL, AlloyDB, Spanner, Kubernetes, Docker, GCP, OpenTelemetry, Kafka, and more.
Open Roles:
- Senior Software Engineer ($165k–$185k)
- Senior Software Engineer – Front End ($145k–$160k)
I also have this question, ads for remote should include either timezone requirements or geographical requirements, otherwise everyone wastes their time
Other than the flourish of adding some Scala to enterprisey Java there is absolutely nothing atypical about this bog enterprisey application. It’s a JS/TS/Java app, nothing else stands out.
Listing every config language and a few lines of CI or whatever scripts shit is misleading.
I see nothing other than typical boring enterprise/big gov crap here (which is fine, and expected).
I don't see how to configure anything but an interval (e.g. every N minutes) in checklyhq. Deadcheck allows you to expect check-ins at arbitrary times (e.g. 9am, 1:15pm, 3:15pm on weekdays).
Systems always rely on something. PagerDuty has been very reliable for years and we use it for alerting, so relying on it more isn’t a big ask. I plan to support multiple integrations so you could get alerted from multiple streams.
Plus the demo's computation happens client side so no data is sent to a server.
We can offer our full payment parsing libraries to the web as developer tools without any code changes. I don't have to care about the details of WASM because it "just works".
https://moov-io.github.io/ach/webui/
reply