FizzBuzz Enterprise Edition
Koa
Our great sponsors
FizzBuzz Enterprise Edition | Koa | |
---|---|---|
329 | 71 | |
20,374 | 34,767 | |
1.4% | 0.3% | |
0.0 | 5.4 | |
5 months ago | 8 days ago | |
Java | JavaScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
FizzBuzz Enterprise Edition
-
Simple Lasts Longer
That "Hello World Enterprise Edition" looks dangerously under-engineered - I could understand it! Far better to follow the best practices demonstrated in the Fizz Buzz Enterprise Edition...
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
-
Writing Clean Code with FastAPI Dependency Injection
Clean code is a balancing act - you’ll want to make sure you don’t turn your codebase into something like this.
- Milyen hasznos Github repokat ismertek?
-
Java 21 makes me like Java again
???
I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)
I'm guess that to those of us who remember when Java came out, "FizzBuzz: EE" is what we think of when we think of Java. :P
In Java I have to type a bazillion characters to get anything done! And make all these useless directories and files and InterfaceClassFactoryProtocolStreamingSerializer BS. And worry about how that executes.
C++? No bloat*, just speed
*Yes, there's some _optional_ bloat. But compared to Java? no contest.
-
No One Wants Simplicity
There’s a difference between complexity that’s inherent to the problem, and complexity that’s added by developers who have drunk architectural cool aid.
This is an example where all of the complexity is caused by rigid adherence to the most popular architectural patterns of about 10 years ago.
https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
It looks completely ridiculous to modern eyes, but during peak OOP it was just how you should do it.
If you like simplicity then your fizz buzz implementation would be a few lines.
-
55 GiB/s FizzBuzz (2021)
maybe it's fast, but is it enterprise quality? https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
Another half-backed dependency injection crate
Nope, I wouldn't use it. I've seen many projects that use DI containers in my career, and every single one of them was a pain to navigate, particularly when trying to get a foothold as a newcomer. It can also force you into some very enterprise-y code patterns. Keep things simple. My mantra is "Add complexity as you find that you need it, and not a second sooner".
-
I'll use a hashmap 😛
Do you want a quick hack or a coder that's up to enterprisey standards? A proper solution could be in the 1.5 KLOC ballpark...
-
Is sequential IO dead in the era of the NVMe drive?
> you have no idea how much happens so your transaction doesn't get lost, corrupted, or errored out.
Maybe he doesn't, maybe he does - you don't know nor do I.
I'm pretty sure this is how IBM salesmen used to respond when confronted with those newfangled Unix systems which were starting to appear here and there, nibbling first, then taking larger bytes out of their market share. Instead of the litany of diverse systems they'd have thrown LPARs, SYSPlexs and ESMs around but in the end it still came down to the same thing: this stuff is too complicated to be left to amateurs. They were right, in a way... until those amateurs grew their wisdom teeth and took a large part of their market away from them.
Yes, "enterprise" stuff is complicated - often overly so [1] - and it has its place. This does not make it the only viable solution to these problems, something will eventually come up to eat your lunch just like IBM saw its herd of dinosaurs being overtaken by those upstart critters from the undergrowth. Maybe some smart software system which "guarantees" data reliability and availability without the need for "enterprise" storage devices? It wouldn't be the first time after all.
[1] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
Koa
-
Hono vs. H3 vs. HatTip vs. Elysia - modern server(less) replacements for Express
Since "Express.js is an old framework that has not evolved for a long time. It's not a good choice for new projects since it can easily lead to security issues and memory leaks." -- H3. Which is also the case for Koa.
-
Instrumenting AWS Lambda functions with OpenTelemetry SDKs
In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.
-
Server-side Rendering (SSR) From Scratch with React
The initial step is to create our entry point, from where the page will be rendered. In this case, we will use the koa framework.
-
The Ascent of Node.js: How a runtime changed the Web
Koa.js: By the team behind Express, Koa.js utilized async/await for middleware, resulting in cleaner and more readable code.
-
Stop using express.js
Koa
-
Node.js Developers: The Key Players in Building Fast and Scalable Web Applications
Koa.js: https://koajs.com/
-
Node JS Microservice Frameworks for Developing Scalable Web Apps.
Koa -Next Generation Node Microservice Framework
-
What is your ideal setup for new project for solo developers
Backend is more tricky. - RESTful APIs I prefer Koajs - For a RPC/microsevice, I have only used gRPC - For a CLI, yargs and inquirer
-
Why I selected Elixir and Phoenix as my main stack
There are lot of different frameworks out there. If you learn one, there is no guarantee that the next job you find will use the same. For example if you learn Express and the next one used Koa or Nest.
-
10 Node.js Frameworks Every Developer Should Know
Koa.js is a minimal and flexible Node.js web application infrastructure, which provides a robust set of features for web and mobile applications. It is an open-source framework developed and maintained by the creators of Express.js, the most popular web framework for Node.js.
What are some alternatives?
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
Next.js - The React Framework
fastify - Fast and low overhead web framework, for Node.js
Express - Fast, unopinionated, minimalist web framework for node.
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
feathers - The API and real-time application framework
AdonisJs Framework - AdonisJS is a TypeScript-first web framework for building web apps and API servers. It comes with support for testing, modern tooling, an ecosystem of official packages, and more.
deno - A modern runtime for JavaScript and TypeScript.
hono - Fast, Lightweight, Web-standards
tsoa - Build OpenAPI-compliant REST APIs using TypeScript and Node
AWS Lambda Router for NodeJS - AWS Lambda router for NodeJS
benchmarks - Fast and low overhead web framework fastify benchmarks.