Live data from Hacker News

Show HN: Vyne – Automated API Orchestration

vyne.co

11–17 of 17 posts

Re: Show HN: Vyne – Automated API Orchestration

#13

Really interesting project and will be very keen to keep our eyes out on progress. I think it would be very useful for us if Vyne becomes like a Zapier and easily lets us hook into other systems.

Seconded. If the underlying Vyne core is solid, and provides an API a JS frontend can interact with, you could have your own integration service up and running fairly rapidly.

Re: Show HN: Vyne – Automated API Orchestration

#14

Hi HN. Vyne is my project. It's still early days, but I'm excited to share the MVP. Vyne itself is platform agnostic, and will work with any HTTP based API (with other integrations planned). There's a decent SDK for Spring Boot projects, which makes getting started as easy as a couple of annotations. This will be broadening to other platforms shortly. Happy to answer any questions, and feedback warmly received.

Very glad to see this. Good luck!

Re: Show HN: Vyne – Automated API Orchestration

#16

I had no idea about eurkea

It's pretty popular in the Java / Spring community, as Spring makes service discovery with Eureka dead simple. There's a bunch of tooling from the Spring Cloud / Netflix stack that gives you a huge amount of functionality for very small amount of code. That said, Vyne isn't coupled to Eureka, it's just where I've started. I'll be exploring other discovery platforms & service meshes soon.

You could probably leverage the service discovery APIs in Envoy to make this more stack-agnostic. Just a thought.

Re: Show HN: Vyne – Automated API Orchestration

#17

Earlier quoted context omitted.

Any plans to support Node+Express setups ? BTW, you can probably simplify the pricing page. Currently there are lot of features in the paid plans without much background info on.

Absolutely, and I've had a cursory play with this. The big challenge is the lack of type data, which makes the upfront plumbing kinda painful. The ideal setup would be to leverage Typescript's type data to generate the schemas, for those who have written their API's in TS. However, that requires hooking into the compilation phase, and I haven't had time to explore that in anger yet. I know that getting a great soluti…

Might also be source for inspiration: https://github.com/epiphone/routing-controllers-openapi
Post reply on HN