ASP.NET Core Reviews

goa Reviews

ASP.NET Core mentions (5)

• The Case For Go Backends

  However, usage of a C# framework like ASP .NET Core or a Java framework like OfficeFloor are more than capable in the right hands. The key is to understand the tradeoffs of each language and framework, and to choose the right tool for the job. - Source: dev.to / over 2 years ago

• Exploring Xperience By Kentico: Introductions

  The administration UI is now built on React and ASP.NET Core which means it's fast 🚀! - Source: dev.to / almost 3 years ago

• Trying to learn ASP.NET core, but confused by the documentation

  Per https://dotnet.microsoft.com/en-us/learn/aspnet/what-is-aspnet-core, "ASP.NET Core is the open-source version of ASP.NET, that runs on macOS, Linux, and Windows. ASP.NET Core was first released in 2016 and is a re-design of earlier Windows-only versions of ASP.NET.". Source: over 2 years ago

• How can I convince my boss not to use Windows Server?

  But how about you both get your wishes: ASP.NET Core? Use a Linux server - with which you are familiar with, to host the live/production version. And the web application itself can be locally developed and tested in ASP.NET on a Windows server, which is what your boss wants? Source: over 3 years ago

• 3 Different Hosting Models in Blazor

  Let’s remember that ASP.NET Core is cross-platform and can run practically anywhere. If you find yourself using C # for all your development, this is probably the best scenario for you to use anyway. With it, you can deploy your web application, which would also contain your Blazor Wasm assets in the same location. - Source: dev.to / about 4 years ago

goa mentions (27)

• IBM to Acquire HashiCorp, Inc

  My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / about 1 year ago

• Microservices communication

  See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: over 1 year ago

• Which is the best framework to create web apps with go?

  If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: almost 2 years ago

• OpenAPI v4 Proposal

  Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 2 years ago

• Beginner-friendly API made with Go following hexagonal architecture.

  One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: about 2 years ago