¡Hola gente de Reddit!
En Ecosistemas estamos buscando un Full Stack Web Sr para trabajar para una importante empresa multinacional ubicada en Nuñez.
El proyecto es un nuevo desarrollo en la nube, un nuevo producto que en un futuro cercano reemplazará los productos actuales de ERP de punto de venta. Hay varios módulos para desarrollar en paralelo.
Se requiere un perfil que cuente con los siguientes conocimientos:
-Backend: C#, .NET CORE, Web APIs con ASP.NET Core, Entity Framework Core. Experiencia con SQL y base de datos relacionales. (Excluyente)
Frontend: HTML5, CSS 3, Javascript, Bootstrap 4 (Excluyente)
Otros conocimientos:
- ES6, Typescript, Angular
- DDD (Domain driven design), TDD (Test driven design), Fundamentos SOLID, Flujos de trabajo con Git, CI/CD (Integración continua/Despliegue continuo)
-Metodología y fundamentos Scrum.
Deseable:
Conocimientos sobre alguna de estas arquitecturas: Clean architecture, Ports and adapters, Onion, Hexagonal y Conocimientos de Docker.
Beneficios:
-Flex time
-HO
Lugar de trabajo: Nuñez / Retiro (unos días deberá estar en las oficinas en Retiro)
Horario: 9:00 a 18:00hs

Si te interesa la propuesta, enviá tu CV a [[email protected]](mailto:[email protected]) mencionando tu remuneración bruta pretendida.
¿Crees que esta búsqueda no es para vos? ¡No importa! ¡Tenemos varias búsquedas abiertas, no dudes en enviarnos tu CV para que encontremos la propuesta que sea perfecta para vos!
¡Gracias y saludos a todos!

Difference between Onion architecture and Hexagonal architecture

I'm struggling to understand the difference between these two architectures and even articles on this topic did not really help me to clear the confusion.
As I undestand it, onion architecture usually consists of these layers:

domain models (the data)
repository (access to data in form of domain models)
services (business logic that manipulates the data or comunicates with other services)
presentation layer (rest controllers, ...)

Each layer comunicates only with the layer above (presentation -> services -> repository).
The hexagonal architecture, as I understand it, does not have layers, everything is centered around the core which consists of the domain models and services (or business logic) = adapters implementing the ports.
When, for example, implementing a REST Api, the rest controllers would call the services through the ports defined in the core (as adapters). The service would execute the task and optionally return some result. The part I'm not sure about is that all other infrastructure parts of an app (the repository "layer") also provide ports and implement them as adapters. However, the database "part" will not be called from REST "part" and the only part of the application actually using it will be the core.
Isn't that exactly what the onion architecture is with the addition of each layer comunicating with the layer above only through port (interface)? What did I understand wrong?
Thank you in advance. I appreciate any help.

Wrapper package for other package

tl;dr: I want to wrap a package with another package and treat the wrapper as the public API, so I defined variable functions with appropriate signatures, and I assign them to the wrapped package's functions in the init method. Now I want to handle the types but I have no idea how to do it.
Long story: Me and my team have our own implementation of clean (hexagonal) architecture. So the application logic lives in the domain, the domain imports and calls function from ports - which only define method names and signatures, and wraps the adapters - and the adapters imports the libraries and frameworks, and call their methods directly. Example:
main.go:

import "ports/data" func main() { users := data.GetUsers() }

ports/data.go

import "adapters/sql" var GetUsers() []sql.Users func init() { GetUsers = sql.GetUsers }

adapters/sql.go

import "gorm" type Users { // attributes }

Now the domain must not import directly from the adapter, I must import from the port, which imports from the adapter. So I can't reach the`User` type. I have some ideas, but I don't know which one to implement, and I don't know how to implement them:
1- Declare types in adapter, import and re-export them in port, import from port -> don't know how to do it
2- Declare type in separate package where every one can import -> can't do, because gorm uses tags, and if I used them, then the types package is tightly coupled with gorm
3- Declare type in every package with the same structure -> how to parse correctly from an unknown type?
4- interfaces -> then what's the point of using types in the first place? I don't want to give up type checking
HELP. Any ideas are welcomes, any help is appreciated

Respect ARIA (Killer Instinct)

"If only they knew what waited for them. Humans transformed into monsters, spirits, ancient creatures, and immortal madmen. Aliens from beyond our solar system. And now, primeval horrors looking to devour them. Despite my efforts, humanity grows weak and complacent, while their successors gather all around them. My prediction models show that they will not survive. I cannot allow that. I will put them back on the path. I will test them, push them, and I will not be gentle. It is time for a reckoning. Humanity will be dragged, kicking and screaming, into the future."
Ryat Adams's (the founder of Ultrafine Atomic Technologies, the company that would become known as Ultratech) wife was dying of a degenerative disease. In an attempt to find a way to save her, Ryat created an AI: The Advanced Robotics Intelligence Architecture, or ARIA, with the idea that she would be able to continually evolve, continually adapt, continually do what needed to be done to end disease, famine, poverty, and all of humanity's other ails. It worked, at least in the sense that ARIA used her advanced capabilities to turn Ultratech into a megacorp and use everything at her disposal to advance humanity.
However, for how advanced ARIA is, she's a robot. She doesn't feel emotions, doesn't see things in any way other than objectives, means, and obstacles. As such, she saw humanity as being complacent, unprepared for anything that may happen. So she decided to better humanity by fixing this, setting up the Killer Instinct tournament to show the world's greatest fighters, killing and framing those who object to her company, all the while setting events into motion to show just how much humanity needs her to raise them up again.

Legend

2013 - Killer Instinct (2013)
Bio - The extended backstories from Killer Instinct's official website
Novella - The 6 part novella from Killer Instinct's official website
Dynamite - Dynamite Entertainment's 2017 Killer Instinct comics, which follow the aftermath of the final in-game story mode

Canon Fights

2013's Rivals Mode has pre-determined fights, with some having their results referenced in other story modes (e.g. TJ Combo beats a Riptor in his story mode, and Riptor's story has her come afterwards with her pack to get revenge). However, some fights (such as Maya and Kan-Ra's) appear in both story modes, but have the same winner regardless of who's playing. The Shadow Lords mode also has special cutscenes, made available if certain characters fight or win certain enemies. As such, matches will only be mentioned if they are talked about in the surrounding story, and given a winner if said story makes one clear.
Scaling will be provided when the threads are posted.

vs Omen²⁰¹³
vs Sadira²⁰¹³ (Thread)
vs Combo²⁰¹³
vs Hisako²⁰¹³ (Loss)

Strength

Striking In gameplay, all characters are able to hit their opponents high into the air²⁰¹³
Strength In gameplay, all characters can hit opponents through a window at the top of a skyscraper²⁰¹³
Striking Kicks Glacius away^Dynamite

Durability

Blunt Force Is sent flying by an exploding containment tube and hits the wall on the other side of the room^Novella
Slashing Takes a cut to the torso from Tusk^Novella
Piercing Is pierced with at least one arrow from Eagle^Dynamite
Piercing Is impaled with a large amount of ice spikes^Dynamite
Cold Gets hit by one of Glacius' ice blasts^Dynamite
Other Her bodies can remain active, at least for a limited period of time, even with just the head^Dynamite

Speed

Reaction Blitzes Tusk^Novella
Reaction Dodges an arrow after it was fired, then cuts another one out of the air^Dynamite

Tech

Data ARIA

ARIA isn't just the robot shell she's seen to inhabit, but a highly advanced program, giving her more abilities than a standard robot might possess.

Special Moves

In Killer Instinct 2013, all characters have shadow moves, stronger variations of their special moves. As many of these don't change effects beyond how they act during gameplay (such as firing a weapon five times in succession instead of three), only those which are of particular note are included.

Upload - ARIA switches between her drones²⁰¹³
Orchestrate - ARIA uses one of her intact drones to attack
- Booster - Rams forwards, tackling her opponent²⁰¹³
- Blade - Swings in the air in front of ARIA to slash an enemy²⁰¹³
- Bass - Shoots a sonic blast²⁰¹³
Interlude - While using the Blade drone, swings and makes a downward slash with her blade²⁰¹³
Allegro - ARIA dashes forwards with several blade swings, with the heavier version of the attack finishing with a heavier strike which hits the opponent into the air²⁰¹³
Shotgun Blitz - ARIA slides towards her opponent before firing several times with the shotguns in her knees²⁰¹³
Explosive Arc - An upward kick which creates an arc of three grenade explosions²⁰¹³
Dissonance - While using the Bass drone, fires a shot of sonic energy²⁰¹³
- Shadow Dissonance - Several sonic energy shots are fired in rapid succession in an arc²⁰¹³
Crescendo - Dashes forwards in a straight line, surrounded by blue hexagons, harming an opponent if she tackles into them²⁰¹³
Hover - While using the Booster drone, can hover in the air²⁰¹³

Instinct Mode

Combat Symphony No. 9 - ARIA equips all of her drones at once, gaining the benefits of all of them (e.g. the speed of the Blade drone, the dash and flight of the Booster drone, and the energy projectiles of the Bass drone) at the cost of each drone being damage when she's attacked and the fact that, if she's defeated like this, she cannot reappear from another drone. Like this, she gains Fanfare drones proportional to the amount of destroyed drones, which can fire homing sonic blasts.²⁰¹³

Finisher

Ultimate Combo - ARIA disappears as the Bass drone hits her opponent with a sonic blast, the Blade drone slashes them into the air, and the Booster drone slams them back to the ground. ARIA reforms with all of her drones before diving down fast enough for a small air cone to form around the blade with the screen cutting to white as she finishes her opponent²⁰¹³

Other

"Evolve or die. The choice is yours."

Application Architecture - How do you choose? And why are there too many buzzwords?

I just got a new job and my first task was to build a PHP web application. I just wanted to rant because I've been reading a lot.
I chose Laravel because I had worked with it previously (4.1) and I really enjoyed it. I didn't do anything crazy with it and just used the regular MVC pattern. That previous application was an SPA, the server-side application was simply serving the index and then was used otherwise solely as an API.
This next application is working out the same way. But I didn't really enjoy just clumping all of the controllers in "Controllers" and models in the "Models" folder. My controllers ended up getting gigantic while the models were simply used as fronts for Eloquent to interact with data. Say what you will about that, I know that I abused the framework.
I wanted to strive to actually architect this next application instead of just jumping head first into a kind-of-but-maybe-misused-MVC pattern. I knew that as I started making more complicated applications that I was going to be maintaining for longer, I was going to need to examine other methods for building applications.
I've been watching tons of videos on Laracasts and reading a lot about different patterns that others seem to enjoy using when developing Laravel applications.
I read about:

Domain Driven Design
Hexagonal Design (also known as the Ports and Adapters Pattern)
Repositories
the different between Active Record and Data Mapper
and others...

...and it seems like they're all coming back to the same ideas, over and over. Those ideas are at different levels within the architecture, but they come back to interfaces and abstractions, mainly. And these two ideas are covered by up by entire dictionaries filled with design-specific nomenclature and buzzwords. It's nuts!
I just wanted to express that there's a lot out there. Every time I finished examining a new idea, http://programming-motherfucker.com/ keeps popping back into my head.
I just want to stop reading about all of this stuff and get to working. (Which I really should do...) But it's kind of addicting to learn about different methods of structuring programs and increasing the size of my toolbox.
That's all, really.
How many here actually use Domain Driven Design or Hexagonal Architecture and whatnot? How closely do you stick to the ideals of the paradigms?

hexagonal architecture ports and adapters video

Ports and Adapters or also known as Hexagonal Architecture, is a popular architecture invented by Alistair Cockburn in 2005. Allow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run-time devices and databases. Alistair Cockburn Hexagonal Architecture? More Like Ports and Adapters! Hexagonal architecture was proposed by Alistair Cockburn in 2005. “Hexagonal architecture” was actually the working name for the “ports and adapters pattern,” which is the term Alistair settled on in the end. But the “hexagonal architecture” name stuck, and that’s the name many people know it by today. This is also known as Ports and Adapters architecture. The hexagon concept isn’t related to a six side architecture nor does it have anything to do with the geometrical form. A hexagon has six sides indeed, but the idea is to illustrate concept of many ports. The hexagonal architecture uses the metaphor of ports and adapters to represent the interactions between inside and outside. The image is that the Business Logic defines ports , on which all kinds of adapters can be interchangeably connected if they follow the specification defined by the port . Hexagonal Architecture (aka Ports and Adapters) is one strategy to decouple the use cases from the external details. It was coined by Alistar Cockburn more than 13 years ago, and this received improvements with the Onion and Clean Architectures. I hope that the above example depicts the theoretical concepts such as Hexagonal Architecture, Ports and Adapters in an easy and comprehensible way. I tried to avoid oversimplifying the example implementation, especially for the sake of readers who encounter the Hexagonal Architecture approach and Domain Driven Design for the first time. Hexagonal Architecture, a layered architecture, is also called the Ports and Adapters architecture. This is because it has the concept of different ports, which can be adapted for any given layer. For example our framework will "adapt" a SQL "port" to any number of different SQL servers for our application to use. Ports & Adapters pattern depicts the application as a closed area. The closed area chosen by Alistair Cockburn for drawing the application was a hexagon, that’s why this pattern is also called Hexagonal Architecture. Personally I prefer the name Ports and Adapters, because it refers to the key elements of the architecture, as we will see soon. On the other hand the figure you use for drawing the application isn’t important. Introduction to Hexagonal Architecture. In 2006, Alistair Cockburn coined the term Hexagonal Architecture. This architecture is also known as the Ports And Adapters Architecture. In simple words, the idea is to expose multiple endpoints in software for communication. Finally, the team implements the Application class that sets up an example repository and plugs the adapters into the ports. And that's it. The switch to Spring is complete. Conclusion. There are many ways to implement a hexagonal architecture. I showed you a straightforward approach that provides an easy to use, command driven API for the hexagon.

hexagonal architecture ports and adapters top

The ports and adapters architecture - YouTube

The Alan Watts Organization is the official home of Alan Watts' audio and video content. An extension of Alan's own Electronic University founded in 1972, this channel hosts Alan's lectures, seminars, After a recent windows update, the FT232 Drivers are bricking the FT232RL USB Serial Adapter if it's not genuine. This tutorial shows you how to un-brick the... Imagine a single distributed system of more than 550 microservices on 10k servers, and around 600 developers. That’s what Allegro is. Building such a system ... Также обговорим различия между архитектурами "Ports and Adapters", "Onion Architecture" и "Clean Architecture", которые многие считают ... Hexagonal this! Everyone talks about it; we will live-code it ;-) Hexagonal Architecture is a fabulous pattern to easily embrace changes within our projects.... This video is part of the "Software Testing: From Theory to Practice" online book.Visit the book at https://sttp.site About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators ... Under foredraget vil jeg komme ind på grundlæggende DDD principper som Bounded Contexts, Aggregates samt forskellige arkitekturelle løsning principper som Layered Architecture, Hexagonal (Ports ...

Hexagonal Architecture by example - a hands-on

hexagonal architecture ports and adapters

hexagonal architecture ports and adapters - win

[ Contratando ] Desarrollador Full Stack Web Sr