eandre

8 ms·

61.
by eandre 5y ago
I grew tired of always looking up the magic invocation to add, remove, upgrade dependencies, so I assembled all the stuff you need to know to use Go modules effectively on a single page. Hopefully it's helpful to others!
62.
Go Modules Cheat Sheet(encore.dev)
3 points by eandre 5y ago|1 comments
63.
by eandre 5y ago
It might be like rails in the sense of prioritizing the developer experience, but the goals are quite different. Rails is a web framework designed to build websites. Encore is a backend framework designed to build distributed systems. In pr
64.
by eandre 5y ago
No, we do support storing secrets and securely delivering them to the running application. See `encore secret set --help`.
65.
by eandre 5y ago
If that works for you, all the better! There are quite a few things that Encore does beyond what you mentioned: - Automatically sets up dedicated Preview Environments for your Pull Requests - Provisions all the infrastructure you need, both
66.
by eandre 5y ago
Good questions! "Encore Cloud" is currently deployed to AWS and DigitalOcean under the hood. As for being tied to us, that's a big part of why we're open sourcing it. We see that Encore can rather reduce lock-in, as the
67.
by eandre 5y ago
Fair enough :) We're working on adding GraphQL support as an alternative approach to exposing your API, and what you suggested wouldn't be that difficult to add either.
68.
by eandre 5y ago
Since Encore supports deploying to your own cloud, it's definitely possible to integrate with existing systems you already have in place. We're also working on expanding the set of infrastructure primitives supported, so that you
69.
by eandre 5y ago
It's like gRPC in the sense that it's endpoint-centric rather than URL-centric.
70.
by eandre 5y ago
Thanks for the feedback. I think there are many different types of magic. In my (biased) opinion I think the code generation we do is much more on the side of "how to do this is obvious but annoying" rather than on the "I don
71.
by eandre 5y ago
Thanks! Encore does support dropping down to plain HTTP requests which lets you use Websockets, see [1]. We hope to make it more ergonomic and less boilerplate-y in the future, but it is supported :) [1] https://github.com/e
72.
by eandre 5y ago
Currently Encore deploys to Kubernetes, and uses Terraform under the hood to provision the infrastructure. Over time we'll add much more flexibility in how you deploy the application and the infrastructure we support. It's not ano
73.
by eandre 5y ago
A lot of the seminal research papers are surprisingly readable! I really recommend reading them to get a good feel for the sort of problems you face at scale and good ways of handling them. Off the top of my head: a lot of stuff from Google
74.
by eandre 5y ago
I've been working on Encore for the past 3 years. I was at Spotify for the past 8 years as a Staff Software Engineer. We grew frustrated with the disproportionally large effort needed to build even simple backend applications, and crea
75.
Show HN: Encore – Go framework for building distributed systems(github.com)
182 points by eandre 5y ago|69 comments
76.
by eandre 5y ago
Thanks! Yes, it's quite unlike other frameworks :). We also provide a complete cloud platform that provides things like CI/CD, secrets management, GitHub integration and more.
77.
by eandre 5y ago
Yes, it analyzes your code and builds up a really detailed understanding of what your app does. We use that analysis to do a bunch of stuff: - Automatically provision cloud infrastructure - Generate API Documentation and type-safe clients t
78.
by eandre 5y ago
Hey HN, I've been working on this framework for the past 3 years because I grew frustrated with how slow it is to build backend applications. Encore offers a different approach to backend development, heavily based on static analysis a
79.
Show HN: Encore – Go backend framework with superpowers(github.com)
11 points by eandre 5y ago|5 comments
80.
by eandre 5y ago
We use it as part of mTLS to provide access to application metadata. It doesn't need to be SPIFFE but it made sense for our use case :)
81.
by eandre 5y ago
I don't disagree,but I think there's space for several levels of abstraction between where we are today and no-code tools.
82.
by eandre 5y ago
TLS always felt like a scary beast to me until I started writing Go. The crypto/tls package is amazing and makes doing incredible things with TLS super easy. We're using it in lots of interesting ways behind the scenes for Encore,
83.
by eandre 5y ago
Agreed completely. Today there's such a large disconnect between how you think about software (APIs, services, systems, data flows, replication, data storage, access patterns, and so on) and how you actually develop software, with pl
84.
by eandre 5y ago
In the ideal case it should be constant and as close to zero as possible! Of course we don't live in that world for arbitrary scale, but surely "a one person SaaS" should be able to do without so much low-level tech and infra
85.
by eandre 5y ago
The most natural way is to join a startup that is scaling. You can of course learn by doing it yourself on the side, but in practice "learning by doing" on the job is by far the most effective in my experience. I also hope we don&
86.
by eandre 5y ago
Super interesting! Definitely feels like a lot of fairly low-level tech to have to deal with for a one-person company, but I guess that doesn't surprise me any more :)
87.
by eandre 6y ago
It seems to me that it should be possible to operate a public transit system profitably if you assume a steady state, meaning no need to expand. But when cities grow, public transit systems must continually expand to continue to service the
88.
by eandre 6y ago
This submission comes at the perfect time. I've been working on improving the docs for Encore for the past week, and while I was aware of different types of documentation, this does an excellent job breaking it down and making it concr
89.
by eandre 6y ago
For a long time I've felt there are a plethora of communities for frontend development, but little for backend development. Any recommendations on backend-oriented communities?
90.
by eandre 6y ago
In my experience languages have a culture of their own. For example, C++ has a culture of caring about low-level details to squeeze out maximum performance. I once found myself writing something that wasn't performance critical in C++

More ›