Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Vyne – Automated API Orchestration

vyne.co

Post reply on HN
Print view View original

1–10 of 17 posts

Re: Show HN: Vyne – Automated API Orchestration

#2

Post by martypitt »

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.

Re: Show HN: Vyne – Automated API Orchestration

#3

Post by option_greek »

martypitt wrote: post #2

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 interesting project. I think you should probably mention the tech stack details in the front page. Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something). Given a rest service output, can't some of these things be auto generated ?

Re: Show HN: Vyne – Automated API Orchestration

#4

Post by martypitt »

option_greek wrote: post #3
martypitt wrote: post #2

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 interesting project. I think you should probably mention the tech stack details in the front page. Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something). Given a rest service output, can't some of these things be auto generated ?

Thanks!

> Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something).

The goal is to keep this type of rework minimal-to-none, by leveraging the type data that's already there. In typed languages, if the contracts are well typed, then you're already 90% of the way there.

> Given a rest service output, can't some of these things be auto generated ?

Exactly. For example, Vyne can work with a plain old swagger file, which many services already have. From there, it's a little additional metadata to identify ID's etc.

However, the idea is that getting Vyne working should be much less code than the alternative - which is to write the integration code manually. Also, getting Vyne going is a one-off cost, which should remain robust as the surrounding services change their APIs.

Re: Show HN: Vyne – Automated API Orchestration

#6

Post by option_greek »

martypitt wrote: post #4
option_greek wrote: post #3

Earlier quoted context omitted.

Very interesting project. I think you should probably mention the tech stack details in the front page. Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something). Given a rest service output, can't some of these things be auto generated ?

Thanks! > Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something). The goal is to keep this type of rework minimal-to-none, by leveraging the type data that's already there. In typed languages, if the contracts are well typed, then you're already 90% of the way there. > Given a rest service output, can't some of these things be auto generated ? Exactly. For…

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.

Re: Show HN: Vyne – Automated API Orchestration

#7

Post by option_greek »

option_greek wrote: post #6
martypitt wrote: post #4

Earlier quoted context omitted.

Thanks! > Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something). The goal is to keep this type of rework minimal-to-none, by leveraging the type data that's already there. In typed languages, if the contracts are well typed, then you're already 90% of the way there. > Given a rest service output, can't some of these things be auto generated ? Exactly. For…

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.

edit: My bad - I do see detailed feature info below.

Re: Show HN: Vyne – Automated API Orchestration

#8

Post by martypitt »

option_greek wrote: post #6
martypitt wrote: post #4

Earlier quoted context omitted.

Thanks! > Does seem to take a lot of work to redefine all the types from the existing services (unless I'm missing something). The goal is to keep this type of rework minimal-to-none, by leveraging the type data that's already there. In typed languages, if the contracts are well typed, then you're already 90% of the way there. > Given a rest service output, can't some of these things be auto generated ? Exactly. For…

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 solution for the Node community is really important, I just haven't cracked it yet.

Re: Show HN: Vyne – Automated API Orchestration

#9

Post by martypitt »

kristianpaul wrote: post #5

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.

Re: Show HN: Vyne – Automated API Orchestration

#10

Post by rounce »

martypitt wrote: post #8
option_greek wrote: post #6

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…

Have you looked at Tern[1] for this?

1: http://ternjs.net

Post reply on HN