Architect – A Serverless Framework • Hacker News Board

Re: Architect – A Serverless Framework

#71

Post by xellisx » Tue, Jun 12, 2018, 4:28 PM UTC

brianleroux wrote: post #53

optimuspaul wrote: post #40

Earlier quoted context omitted.

What problems did you solve and how were they solved with your new format? I'm neutral in this argument at this point, so I'd like to hear your justifications. Thanks!

There are many issues with both formats: - JSON has no comments - YAML nesting tends to get deep which makes creating bugs very easy - Both are become hard to read / edit in larger files The primary issue is translating the intent into a machine syntax. The format we landed focused on minimalism to communicate intent. The the file format is the least interesting thing about .arc but one of the most distinctive. An .a…

IIRC JSON 5 has comments and other 'fixes'. Also, '.arc' takes me back to the 80s and bbsing.

Re: Architect – A Serverless Framework

#72

Post by RangerScience » Wed, Jun 13, 2018, 1:17 AM UTC

sbr464 wrote: post #47

RangerScience wrote: post #18

Earlier quoted context omitted.

YAML is far easier for humans, and has a few advanced features (node references) that are REALLY nice for any kind of configuration, since you can re-use blocks. Let's say you have to define a bunch of services, with mostly the same environment variables. You can make a "defaults" node, and then a) reference that node in the service descriptions to re-use those env vars, and b) selectively override those defaults in…

That's good to know, thanks for that tip. I've been using secrets with Kubernetes for sharing things currently, but only in small cases.

It's super useful. There's a way to reference a node that just places that node as a child, whole cloth, and another way that merges the node reference with the local node.

This is useful, say, if you're actually de/serializing objects and want to maintain actual references, or if you're just trying to share data between nodes.

Re: Architect – A Serverless Framework

#73

Post by brianleroux » Wed, Jun 13, 2018, 2:18 PM UTC

niteshade wrote: post #67

brianleroux wrote: post #62

Earlier quoted context omitted.

Hey np! Difference of views. No integration w CF is absolutely true but you're also totally free to do that. It doesn't prevent you from using it. No auth support is false. We support session out of the box and you're free to impl any auth scheme of your choosing. Custom file format is being well addressed in other comments. If you don't like it thats fine: enjoy YAML elsewhere. CORS could be implemented in the file…

Hi, thanks for the reply! > No integration w CF is absolutely true but you're also totally free to do that. It just seems then that there is no real way for me as a developer to transfer all the accumulated knowledge I already have about AWS to your framework. Looking through Architect's source, it actually seems as if everything is done via the AWS Javascript SDK, which seems a bit ... odd, to say the least. I'd eve…

Long story short is this existed well before CF support did for Lambda. I don't think you're actually interested in learning and more interested in appearing to know what you're talking about so I'll leave it at that.

Re: Architect – A Serverless Framework

#74

Post by brianleroux » Wed, Jun 13, 2018, 2:24 PM UTC

brianleroux wrote: post #73

niteshade wrote: post #67

Earlier quoted context omitted.

Hi, thanks for the reply! > No integration w CF is absolutely true but you're also totally free to do that. It just seems then that there is no real way for me as a developer to transfer all the accumulated knowledge I already have about AWS to your framework. Looking through Architect's source, it actually seems as if everything is done via the AWS Javascript SDK, which seems a bit ... odd, to say the least. I'd eve…

Long story short is this existed well before CF support did for Lambda. I don't think you're actually interested in learning and more interested in appearing to know what you're talking about so I'll leave it at that.

Also! Killer features galore but folks having trouble seeing past the fmt. You're just making so many assumptions here it's very clear you didn't try it. It's fast.. really fast. Faster than CF.

Re: Architect – A Serverless Framework

#75

Post by brianleroux » Wed, Jun 13, 2018, 3:15 PM UTC

shakna wrote: post #61

brianleroux wrote: post #28

Earlier quoted context omitted.

Author here: we did? Pretty well documented issues w JSON and YAML (coming from CloudFormation perspective). Both have problems (that are unique to each) so we created a format for solving that. If you like JSON and YAML and don't mind those issues you are well served by existing solutions. Cheers!

Your arc format feels a lot like an INI-format, but with one or two teaks here and there. Is it inherently better in a way I'm not seeing? Would arc be suitable enough for a new project to adopt?

I'd like to leave the format discussion behind. Its the least interesting part and you rarely interact with it. I'll add YAML and JSON support so ppl can judge for themselves on merit against options that have tradeoffs.

Its absolutely suitable today. We have it in production in several apps. begin.com and arc.codes itself are two examples that have seen non-trivial traffic.

Re: Architect – A Serverless Framework

#76

Post by keithwhor » Sat, Jun 16, 2018, 4:12 PM UTC

wolfgang42 wrote: post #69

keithwhor wrote: post #65

Earlier quoted context omitted.

Plug that I’m sure Brian won’t mind (he encouraged me to start a company a couple years ago): If you want to get started building serverless functions and APIs quickly, do it in your browser with https://code.xyz - we just released it along with an announcement of our most recent $2M in funding from Stripe [1] who join Slack and others as investors and customers. Disclaimer: I’m the founder. [1] https://stdlib.com/bl…

See, this is exactly the sort of thing I'm complaining about. code.xyz gives some 'hello world' examples, but it doesn't even link to any docs--it just goes "look how easy it is! Here, sign in to our service!" I went hunting for the stdlib docs, and it took me five minutes to figure out how to call my service by HTTP--apparently I just get a special username.stdlib.io endpoint that I can call, but when I clicked 'Cal…

When you run your code a link to your API endpoint is provided immediately: obviously this isn’t clear enough! Thanks for the feedback. We’ll make sure we fix this ASAP. :)

No worries re: frustration. It happens!