Architect – A Serverless Framework
blog.reifyworks.com
Architect – A Serverless Framework
1–10 of 76 posts
Re: Architect – A Serverless Framework
#2Great! Another file format for me to learn.
Why can't everyone use one of the standard file types, like YAML/JSON?
Re: Architect – A Serverless Framework
#3Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
> Architect leverages Node and NPM to finally bring some structure and insight to the AWS Serverless landscape.
But this is the killer Node and NPM framework...
Re: Architect – A Serverless Framework
#4Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
https://serverless.com/ - uses yaml or JSON or js. This looks like an opportunity for the community to grow some more which is almost always a benefit. A new filetype isn't always the best, but it CAN be useful in some contexts, I haven't vetted if this is the right one.
Re: Architect – A Serverless Framework
#5I’m a big fan of code generation. I can usually adapt to new formats or concepts without too much issue. I feel that while it’s not difficult to build up strings dynamically, the harder part can be overwriting and verifying values, and working with logic. That’s my main issue with YAML over JSON. How would you recommend working in this area with this format, or benefits over JSON?
Re: Architect – A Serverless Framework
#6One of the biggest promises that I can see about the serverless movement is:
The ability to have the infrastructure isolated from the raw code being written. (Think more of a grid computing and automatic planning being included)
Unfortunately, I'm not seeing it. I'm seeing that it's heavy on the initial business idea: "Get people to pay more and utilize our servers better".
Re: Architect – A Serverless Framework
#7One of the biggest promises that I can see about the serverless movement is: The ability to have the infrastructure isolated from the raw code being written. (Think more of a grid computing and automatic planning being included) Unfortunately, I'm not seeing it. I'm seeing that it's heavy on the initial business idea: "Get people to pay more and utilize our servers better".
> The ability to have the infrastructure isolated from the raw code being written. (Think more of a grid computing and automatic planning being included)
Can you elaborate? It sounds like you're saying that if you write code that's deployed to a serverless infra you end up with 'serverless code'. This hasn't been my (very limited) experience - where the serverless stuff is just a thin layer around your business logic.
Re: Architect – A Serverless Framework
#8I actually like this. I build serverless apps all the time, mostly manually.
Serverless framework is alright, but I felt it was really bloaty. There was just so much going on. Too many variables and it confuses the user. This looks clean. I might give it a try. I didn't find a link though in your blog.
Re: Architect – A Serverless Framework
#9Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
https://serverless.com/ - uses yaml or JSON or js. This looks like an opportunity for the community to grow some more which is almost always a benefit. A new filetype isn't always the best, but it CAN be useful in some contexts, I haven't vetted if this is the right one.
Yup, serverless works quite well. have used it myself.
Albeit, I'm not fully sold on this whole fake-serverless architecture.
A major part of it is that AWS is arguably frustrating, since the docs are __clearly__ written by marketing people, not engineers. Every aspect feels non-dev friendly.
I would love to see something like Captain Duck Duck, so you can host your own serverless platfrom, sort-of a personalized AWS?
(Captain Duck Duck is a personalized Heroku)
Re: Architect – A Serverless Framework
#10I’m a big fan of code generation. I can usually adapt to new formats or concepts without too much issue. I feel that while it’s not difficult to build up strings dynamically, the harder part can be overwriting and verifying values, and working with logic. That’s my main issue with YAML over JSON. How would you recommend working in this area with this format, or benefits over JSON?
I'm not the creator of this project, but JSON just isn't fun to write. It's readable, but still icky to write. I think to create a format really needs to strike the balance between usability and how natural it is to write. I think ELM for example finds a good balance.