8th Light

8thlight

Hi guys, I’m a Front-End developer. Before there was a time 2 years working CMS Magento, I like CMS Magento because system clean, and architecture database EAV (Entity — Attribute — Value) but I don’t understand why present I’m dev front-end (I don’t know) in the 2-year current. And present I chance comeback working position Back-End that I like. I’ve read some articles following: (Uncle bob) https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html (Iman Tumorang — Software Engineer) https://medium.com/hackernoon/golang-clean-archithecture-efd6d7c43047 (Elton Minetto — CTO) https://medium.com/@eminetto/clean-architecture-using-golang-b63587aa5e3f Summary If you have read through the article Uncle bob, he said that: > Each has at least one layer for business rules, and another for interfaces. So, each of these architectures produce systems that are: Independent of Frameworks. The architecture does not depend on the existence of some library of feature laden software. This allows you to use such frameworks as tools, rather than having to cram your system into their limited constraints. Testable. The business rules can be tested without the UI, Database, Web Server, or any other external element.Independent of UI. The UI can change easily, without changing the rest of the system. A Web UI could be replaced with a console UI, for example, without changing the business rules.Independent of Database. You can swap out Oracle or SQL Server, for Mongo, BigTable, CouchDB, or something else. Your business rules are not bound to the database.Independent of any external agency. In fact your business rules simply don’t know anything at all about the outside world. More at https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html In architecture of Uncle Bob divide 4 layers: Entites Use Cases Controller Framerwork & Devices In my project divide layers: Models Use case Repository Delivery Models: Models is same as entites. It set of data struct, interface and method, functions. Example model: Book ( ) type Book struct {
	ID     uint Title  string Author string }

type BookUsecase interface {
	Fetch(ctx context.Context) ([]Book, error)
	GetByID(ctx context.Context, id string) (Book, error)
}

type BookRepository interface {
	Fetch(ctx context.Context) (res []Book, err error)
	GetByID(ctx context.Context, id string) (Book, error)
} import "context" // Book ... `json:"id" gorm:"primary_key"` `json:"title"` `json:"author"` : Usecase This a layer will handle problem logic business. This a layer decide repository will use. And have responsibility to provide data to layer delivery use.Layer Usecase a depends layer Repository ( )

type bookUsecase struct {
	bookRepo domain.BookRepository
} func NewBookUsecase(a domain.BookRepository) domain.BookUsecase { &bookUsecase{ : a,
	}
}
func (a *bookUsecase) Fetch(c context.Context) (res []domain.Book, err error) {
	res, err = a.bookRepo.Fetch(c) err != nil { nil, err
	} }

func (a *bookUsecase) GetByID(c context.Context, id string) (res domain.Book, err error) {
	res, err = a.bookRepo.GetByID(c, id) } import "context" "github.com/working/project/domain" // NewArticleUsecase will create new an articleUsecase object representation of domain.ArticleUsecase interface return bookRepo if return return return : Repository This a layer will handle to database method: fetch, put, delete, get, etc.Layer responsibility will choose DB use in application. Could be Mysql, Postgresql, MongoDB, MariaDB, etc ( )

type psqlBookRepository struct {
	Conn *gorm.DB
} func NewPsqlBookRepository(Conn *gorm.DB) domain.BookRepository { &psqlBookRepository{Conn}
}

func (m *psqlBookRepository) Fetch(ctx context.Context) (res []domain.Book, err error) { books []domain.Book
	m.Conn.Find(&books) books, nil
}
func (m *psqlBookRepository) GetByID(ctx context.Context, id string) (res domain.Book, err error) { book domain.Book
	m.Conn.Where( , id).First(&book) book, nil
} import "context" "github.com/jinzhu/gorm" "github.com/working/project/domain" // NewMysqlArticleRepository will create an object that represent the article.Repository interface return var return var "id = ?" return : Deliver This a layer will decide how the data present. Could be REST API, HTML, or gRPC whatever the decide type.This a lay accept the input from user and send layer Usecase handle logic ( )

type BookeHandler struct {
	BookUsecase domain.BookUsecase
}

func NewBooksHandler(r *gin.RouterGroup, us domain.BookUsecase) { := &BookeHandler{ : us,
	}
	r.GET( , handler.FindBooks) r.GET( , handler.FindBook) }

func (a *BookeHandler) FindBooks(c *gin.Context) {
	books, := a.BookUsecase.Fetch(c.Request.Context())
	c.JSON( , gin.H{ : books})
}

func (a *BookeHandler) FindBook(c *gin.Context) {
	books, := a.BookUsecase.GetByID(c.Request.Context(), c.Param( ))
	c.JSON( , gin.H{ : books})
} import "github.com/gin-gonic/gin" "github.com/working/project/domain" handler BookUsecase "/books" // r.POST("/books", handler.CreateBook)       // create "/books/:id" // find by id // r.PATCH("/books/:id", handler.UpdateBook)  // update by id // r.DELETE("/books/:id", handler.DeleteBook) // delete by id _ 200 "data" _ "id" 200 "data" Current my project building on based 4 layers: Model, Usecase, Repository, and Delivery which I present above. And my project interview, I think it not good. I will rebuild the architecture project in article next. You should understand architecture someone and accept it in a project of you. That will give you look good and remember to start with it simple Link Project: https://github.com/caohoangnam/go-clean-architecture Tech stack using: Gorm Gin Framework Postgresql Viper Clean Architecture If you have a question , or need more explanation, or something, that I can not explain well here, you can ask me from my linked in or email me. Thank you so much.

Creating Clean Architecture Using Golang

Independent, Testable , and Clean After reading the uncle Bob’s Clean Architecture Concept, I’m trying to implement it in Golang. This is a similar architecture that we used in our company, but a little different structure. Not too different, same concept but different in folder structure. Kurio - App Berita Indonesi a, You can look for a sample project here , a sample CRUD management article. https://github.com/bxcodec/go-clean-arch Disclaimer : I’m not recommending any library or framework used here. You could replace anything here, with your own or third party that has the same functions. Basic As we know the constraint before designing the Clean Architecture are : Independent of Frameworks. The architecture does not depend on the existence of some library of feature laden software. This allows you to use such frameworks as tools, rather than having to cram your system into their limited constraints. Testable. The business rules can be tested without the UI, Database, Web Server, or any other external element. Independent of UI. The UI can change easily, without changing the rest of the system. A Web UI could be replaced with a console UI, for example, without changing the business rules. Independent of Database. You can swap out Oracle or SQL Server, for Mongo, BigTable, CouchDB, or something else. Your business rules are not bound to the database. Independent of any external agency. In fact your business rules simply don’t know anything at all about the outside world.More at https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html So, based on this constraint, every layer must independent and testable. If Uncle Bob’s Architecture, has 4 layer : Entities Usecase Controller Framework & Driver In my projects, I’m using 4 too : Models Repository Usecase Delivery Models Same as Entities, will used in all layer. This layer, will store any Object’s Struct and its method. Example : Article, Student, Book. Example struct : type Article struct {
	ID        int64 Title     string Content   string UpdatedAt time.Time CreatedAt time.Time } import "time" `json:"id"` `json:"title"` `json:"content"` `json:"updated_at"` `json:"created_at"` Any entities, or model will stored here. Repository Repository will store any Database handler. Querying, or Creating/ Inserting into any database will stored here. This layer will act for CRUD to database only. No business process happen here. Only plain function to Database. This layer also have responsibility to choose what DB will used in Application. Could be Mysql, MongoDB, MariaDB, Postgresql whatever, will decided here. If using ORM, this layer will control the input, and give it directly to ORM services. If calling microservices, will handled here. Create HTTP Request to other services, and sanitize the data. This layer, must fully act as a repository. Handle all data input - output no specific logic happen. This Repository layer will depends to Connected DB , or other microservices if exists. Usecase This layer will act as the business process handler. Any process will handled here. This layer will decide, which repository layer will use. And have responsibility to provide data to serve into delivery. Process the data doing calculation or anything will done here. Usecase layer will accept any input from Delivery layer, that already sanitized, then process the input could be storing into DB , or Fetching from DB ,etc. This Usecase layer will depends to Repository Layer Delivery This layer will act as the presenter. Decide how the data will presented. Could be as REST API, or HTML File, or gRPC whatever the delivery type. This layer also will accept the input from user. Sanitize the input and sent it to Usecase layer. For my sample project, I’m using REST API as the delivery method. Client will call the resource endpoint over network, and the Delivery layer will get the input or request, and sent it to Usecase Layer. This layer will depends to Usecase Layer. Communications Between Layer Except Models, each layer will communicate through inteface. For example, Usecase layer need the Repository layer, so how they communicate? Repository will provide an interface to be their contract and communication. Example of Repository’s Interface package repository models type ArticleRepository interface {
	Fetch(cursor string, num int64) ([]*models.Article, error)
	GetByID(id int64) (*models.Article, error)
	GetByTitle(title string) (*models.Article, error)
	Update(article *models.Article) (*models.Article, error)
	Store(a *models.Article) (int64, error)
	Delete(id int64) (bool, error)
} import "github.com/bxcodec/go-clean-arch/article" Usecase layer will communicate to Repository using this contract, and Repository layer implement this interface so can used by Usecase MUST Example of Usecase’s Interface package usecase ( )

type ArticleUsecase interface {
	Fetch(cursor string, num int64) ([]*article.Article, string, error)
	GetByID(id int64) (*article.Article, error)
	Update(ar *article.Article) (*article.Article, error)
	GetByTitle(title string) (*article.Article, error)
	Store(*article.Article) (*article.Article, error)
	Delete(id int64) (bool, error)
} import "github.com/bxcodec/go-clean-arch/article" Same with Usecase, Delivery layer will use this contract interface. And Usecase layer implement this interface. MUST Testing Each Layer As we know, clean means independent. Each layer testable even other layers doesn’t exist yet. This layer only tested if any function/method declared in any of Struct. And can test easily and independent to other layers. Models Layer: To test this layer, the better ways is doing Integrations testing. But you also can doing mocking for each test. I’m using github.com/DATA-DOG/go-sqlmock as my helper to mock query process msyql. Repository: Because this layer depends to Repository layer, means this layer need Repository layer for testing . So we must make a mockup of Repository that mocked with mockery, based on the contract interface defined before. Usecase: Same with Usecase, because this layer depends to Usecase layer, means we need Usecase layer for testing. And Usecase layer also must mocked with mockery, based on the contract interface defined before Delivery: For mocking , I use mockery for golang by vektra could be seen here https://github.com/vektra/mockery Repository Test To test this layer, like I said before , I’m using a sql-mock to mock my query process. You can use like what I used here github.com/DATA-DOG/go-sqlmock , or another that have similar function func TestGetByID(t *testing.T) {
 db, mock, := sqlmock.New() err != nil { 
    t.Fatalf(“an error ‘%s’ was not expected when opening a stub  
        database connection”, err) 
  } 
 defer db.Close() 
 rows := sqlmock.NewRows([]string{
        “id”, “title”, “content”, “updated_at”, “created_at”}).   
        AddRow( , “title ”, “Content ”, time.Now(), time.Now()) 
 query := “SELECT id,title,content,updated_at, created_at FROM 
          article WHERE ID = \\?” 
 mock.ExpectQuery(query).WillReturnRows(rows) 
 a := articleRepo.NewMysqlArticleRepository(db) 
 num := int64( ) 
 anArticle, := a.GetByID(num) 
 assert.NoError(t, err) 
 assert.NotNil(t, anArticle)
} err if 1 1 1 1 err Usecase Test Sample test for Usecase layer, that depends to Repository layer. package usecase_test ( models ucase )

func TestFetch(t *testing.T) { := (mocks.ArticleRepository) mockArticle models.Article
	err := faker.FakeData(&mockArticle)
	assert.NoError(t, err)

	mockListArtilce := make([]*models.Article, )
	mockListArtilce = append(mockListArtilce, &mockArticle)
	mockArticleRepo.On( , mock.AnythingOfType( ), mock.AnythingOfType( )).Return(mockListArtilce, nil)
	u := ucase.NewArticleUsecase(mockArticleRepo)
	num := int64( )
	cursor := list, nextCursor, := u.Fetch(cursor, num)
	cursorExpected := strconv.Itoa(int(mockArticle.ID))
	assert.Equal(t, cursorExpected, nextCursor)
	assert.NotEmpty(t, nextCursor)
	assert.NoError(t, err)
	assert.Len(t, list, len(mockListArtilce))

	mockArticleRepo.AssertCalled(t, , mock.AnythingOfType( ), mock.AnythingOfType( ))

} import "errors" "strconv" "testing" "github.com/bxcodec/faker" "github.com/bxcodec/go-clean-arch/article" "github.com/bxcodec/go-clean-arch/article/repository/mocks" "github.com/bxcodec/go-clean-arch/article/usecase" "github.com/stretchr/testify/assert" "github.com/stretchr/testify/mock" mockArticleRepo new var 0 "Fetch" "string" "int64" 1 "12" err "Fetch" "string" "int64" Mockery will generate a mockup of repository layer for me. So I don’t need to finish my Repository layer first. I can work finishing my Usecase first even my Repository layer not implemented yet. Delivery Test Delivery test will depends on how you to deliver the data. If using http REST API, we can use httptest a builtin package for httptest in golang. Because it’s depends to Usecase, so we need a mock of Usecase . Same with Repository, i’m also using Mockery to mock my usecase, for delivery testing. func TestGetByID(t *testing.T) { mockArticle models.Article 
 err := faker.FakeData(&mockArticle) 
 assert.NoError(t, err) 
 mockUCase := (mocks.ArticleUsecase) 
 num := int(mockArticle.ID) 
 mockUCase.On(“GetByID”, int64(num)).Return(&mockArticle, nil) 
 e := echo.New() 
 req, := http.NewRequest(echo.GET, “/article/” +  
             strconv.Itoa(int(num)), strings.NewReader(“”)) 
 assert.NoError(t, err) 
 rec := httptest.NewRecorder() 
 c := e.NewContext(req, rec) 
 c.SetPath(“article/:id”) 
 c.SetParamNames(“id”) 
 c.SetParamValues(strconv.Itoa(num)) 
 handler:= articleHttp.ArticleHandler{ : mockUCase, : httpHelper.HttpHelper{}
 } 
 handler.GetByID(c) 
 assert.Equal(t, http.StatusOK, rec.Code) 
 mockUCase.AssertCalled(t, “GetByID”, int64(num))
} var new err AUsecase Helper Final Output and The Merging After finish all layer and already passed on testing. You should merge into one system in main.go in root project. Here you will define, and create every needs to environment, and merge all layers into one. Look for my main.go as example: package main ( httpDeliver articleRepo articleUcase cfg _ ) config cfg.Config

func init() {
	config = cfg.NewViperConfig() config.GetBool( ) {
		fmt.Println( )
	}

}

func main() { := config.GetString( )
	dbPort := config.GetString( )
	dbUser := config.GetString( )
	dbPass := config.GetString( )
	dbName := config.GetString( )
	connection := fmt.Sprintf( , dbUser, dbPass, dbHost, dbPort, dbName)
	val := url.Values{}
	val.Add( , )
	val.Add( , )
	dsn := fmt.Sprintf( , connection, val.Encode())
	dbConn, := sql.Open( , dsn) err != nil && config.GetBool( ) {
		fmt.Println(err)
	}
	defer dbConn.Close()
	e := echo.New()
	middL := middleware.InitMiddleware()
	e.Use(middL.CORS)

	ar := articleRepo.NewMysqlArticleRepository(dbConn)
	au := articleUcase.NewArticleUsecase(ar)

	httpDeliver.NewArticleHttpHandler(e, au)

	e.Start(config.GetString( ))
} import "database/sql" "fmt" "net/url" "github.com/bxcodec/go-clean-arch/article/delivery/http" "github.com/bxcodec/go-clean-arch/article/repository/mysql" "github.com/bxcodec/go-clean-arch/article/usecase" "github.com/bxcodec/go-clean-arch/config/env" "github.com/bxcodec/go-clean-arch/config/middleware" "github.com/go-sql-driver/mysql" "github.com/labstack/echo" var if `debug` "Service RUN on DEBUG mode" dbHost `database.host` `database.port` `database.user` `database.pass` `database.name` "%s:%s@tcp(%s:%s)/%s" "parseTime" "1" "loc" "Asia/Jakarta" "%s?%s" err `mysql` if "debug" "server.address" You can see, every layer merge into one with its dependencies. Conclusion In short, if drawn in a diagram, can seen below Every library used here you can change by your own. Because the main point of clean architecture is : no matter your library, but your architecture is clean, and testable also independent This is how i organized my projects, you could argue, or agree, or maybe improve this for more better, just leave a comment and share this The Sample Projects The sample project can seen here https://github.com/bxcodec/go-clean-arch Library used for my project: Glide : for package management go-sqlmock from github.com/DATA-DOG/go-sqlmock Testify : for testing Echo Labstack (Golang Web Framework) for Delivery layer Viper : for environment configurations Further Reading about Clean Architecture: Second part of this article: https://hackernoon.com/trying-clean-architecture-on-golang-2-44d615bf8fdf https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html http://manuel.kiessling.net/2012/09/28/applying-the-clean-architecture-to-go-applications/ . Another version of Clean Architecture in Golang If you have a question , or need more explanation, or something, that I can not explain well here, you can ask me from my linkedin or email me. Thank you

Trying Clean Architecture on Golang

Probando la arquitectura limpia en Golang

A weekly newsletter with the best articles on microservices. Hand-curated by the engineers of . Subscribe: RisingStack https://microserviceweekly.com/ Top 5 Spring + Microservice Courses for Advanced Java Developers In Java world, Spring Framework provides several tools and framework to develop microservices e.g. Spring Boot and Spring Cloud and in this article, I’ll share a couple of good courses you can use to learn how to develop Microservices using Spring framework. _Microservices is the new buzzword in software development word, particularly on Java side, but it’s been in practice…_hackernoon.com Top 5 Spring + Microservice Courses for Advanced Java Developers Operational challenges in Microservices and how to overcome it using Consul In this article we will learn what are some operational challenges in microservices architecture and how consul helps to overcome it. With this we will learn what a service mesh is and how consul helps to overcome the challenges it creates. _In this article we will learn what are some operational challenges in microservices architecture and how consul helps…_devopsideas.com Operational challenges in Microservices and how to overcome it using Consul The Impact of Microservice Architecture on Load Testing See how the structure of microservice architecture and their communication affects the way we need to run load testing. _Microservice architecture (or, "microservices") has slowly emerged in recent years as a go-to method for development…_dzone.com The Impact of Microservice Architecture on Load Testing - DZone Microservices API vs. Microservices: A Microservice Is More Than Just an API A microservice can be misconstrued as simply an endpoint to provide an API. But microservices have much more flexibility and capabilities than that. This article will speak on the differences between APIs and microservices, plus detail some of the benefits a microservice can provide. _When writing software, consider both the implementation and the architecture of the code. The software you write is…_blog.scalyr.com API vs. Microservices: A Microservice Is More Than Just an API From monolith to microservices: Horror stories and best practices Architects currently or formerly at Best Buy, Cloud Elements, and Wix.com share some of the world’s most advanced microservices design escapades — horror stories and best practices from the microservices trenches. _They say software is getting smaller-micro, in fact. Microservices are the latest software architecture trend, and its…_techbeacon.com From monolith to microservices: Horror stories and best practices | TechBeacon Microservices Aren’t Magic: Handling Timeouts As microservices, serverless, and other distributed systems architectures become even more prevalent in the industry, it’s critical that we internalize their problems and strategies for solving them. In this article, we’ll look at one example of the many tricky issues that network boundaries can introduce: timeouts. _Microservices are a big deal. They can give us some pretty big wins for our architectures and teams, but microservices…_8thlight.com Microservices Aren't Magic: Handling Timeouts | 8th Light An Introduction to Serverless Microservices Thinking about microservices, especially their communication patterns, can be a bit of a mind-bending experience for developers. The idea of splitting an application into several (if not hundreds of) independent services, can leave even the most experienced developer scratching their head and questioning their choices. _Thinking about microservices, especially their communication patterns, can be a bit of a mind-bending experience for…_www.jeremydaly.com An Introduction to Serverless Microservices - Jeremy Daly Create full Microservice stack using JHipster Domain Language under 30 minutes Let us see how we can create a microservice stack using JHipster. We will build an e-commerce store today. _It’s been quite a while since I wrote a blog, I did a few some years ago but never really continued writing. So when I…_medium.com Create full Microservice stack using JHipster Domain Language under 30 minutes Training: Designing Microservice Architectures — Barcelona During the course of these two days, we will cover a high-level architectural overview of what is needed to design, develop and maintain an application built with microservices. _Two days of training to master microservices. _ Delivered by the expert instructors of RisingStack. Peter Czibik, Tamas…_ti.to Designing Microservice Architectures - Barcelona In brief Dynamically Update Your Microservice Configuration Serverless Microservices Explained Microservice Architectures in Embedded Linux and FreeRTOS Q&A — Red Hat’s Brian Gracely talks NFV, containers and microservices

The Microservice Weekly #151 — September 26.

Because it’s definition is poorly phrased, the Open/Closed principle is probably the most misunderstood of the 5 SOLID principles. However it’s the one which when properly applied can save you more development effort through good architecture than any of the others. The principle as originated by Bertrand Meyer states: software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification Later, when he included it in his SOLID principles, Bob Martin expressed it better: You should be able to extend the behavior of a system without having to modify that system. What this is about is best understood in the context of writing a software package or library which is used by many third parties. Essentially you want this library to be used in the widest variety of likely contexts by its consumers (open for extension), however you want to change it as little as possible, because every time you do you’re obliging your consumers to update their versions and in the worst case, fix the consequences of breaking changes. Also, this helps with reliability because ideally over time the code will become more and more well tested by use in many contexts, and less and less frequently changed so less liable to be broken by those changes. The same applies to a lesser extent to when you write code in one place in your application which is used elsewhere: if you can adapt it to different purposes by writing new code that is better than modifying it because modifying it will likely cause changes to need to be made everywhere it is used. You can see that this second principle is like the Single Responsibility Principle about minimising the consequences of future changes to your code. And just like the SRP, the way you follow this principle in practice is determined by an educated guess about how the requirements on your software are likely to change in future. In the SRP you make a judgement about decomposition and where to draw encapsulation boundaries in your code. In the OCP, you make a judgement about what in your module you will make and leave to your module’s consumers to make concrete, and what concrete functionality to provide yourself. abstract As with the SRP, this cannot be a one way street where you must write code that could never need to be modified and can always be extended. The only code that could never need to be modified is a class such as below: public class TotallyAbstract<TArg, TRes>{private Func<TArg, TRes> f; public TotallyAbstract(Func<TArg, TRes> f){this.f = f;} public TRes Apply(TArg a){return f(a);}} You’ll notice that it actually has no functionality whatsoever! Here is the opposite: you can only get it to do one thing ever and you’d have to modify it to do anything else: public class TotallyConcrete{public int Apply(){return 2 + 2;}} Any sensible module must lie in between these extremes: to do something useful it has to be partially concrete, however to be used in a range of contexts it must be partially abstract. So don’t get the extremist idea that your code should never be changed only extended! A function or program can have its functionality varied by the parameters and configuration data which it receives. The Open Closed Principle doesn’t seem to be talking about this kind of adaptation of functionality when it speaks of ‘extension’, though. This sounds like writing code not data: however the line between the two is always blurred to a greater or lesser extent. Configuration of a module can be done using data files or code. It’s part of simple programming to call functions with parameters. However, extending code with other code is more advanced. This however is possibly the most important skill to learn as a programmer, because it enables you to write less code! It does this by letting you use the same code in a wider variety of contexts. The skill here is not just in writing code which can be extended easily but also in seeing the opportunity to do so. A very powerful example of this way of working is the plug-in architecture. A classic use for this is in image editors where you can plug in filters made by third parties. The image editor knows nothing specific about any of the filters: it has a contract which is an abstraction which defines the minimum requirements for a piece of code to be used as an image filter, then it makes no further assumptions about the plugins except that they fulfil this contract. This allows the image editor without any of its code being changed to have its functionality extended by other code. Bob Martin writes about this here: . https://8thlight.com/blog/uncle-bob/2014/05/12/TheOpenClosedPrinciple.html This is of course an example of dependency inversion, the D in SOLID. In fact all extension of a module with code is a form of dependency inversion: the difference is in what kind of abstraction you use to specify the dependency which will be injected: The module has parameters in its API which allow functions to be passed in and executed in the context of the module’s operation to specify or modify its function. This is underused in object oriented programming in my view, and provides a clear and simple way to inject code which works best where this function has no need to be reused in other contexts, and is not naturally grouped with a set of related functions as in a class. Function parameters (no data) Similar to the above, except the code which is injected into the module is now in the form of a class which groups together custom methods and possibly data. This is the most recommended approach in object oriented programming, however providing a single function is simpler if appropriate, and a point usually missed is that interfaces, unlike base classes, give the module writer no chance to restrict and control how any of the functionality is provided, which could cause issues. Totally abstract class parameters (interfaces or fully abstract base classes) The client code uses class inheritance to create a subclass which inherits data and some methods from a parent class in the module, adding or changing some methods and adding data as required. Nice to use where there is a hierarchy of more specialised related classes, it can get complicated to manage and so is discouraged by many writers. Partially abstract class parameters (implementation inheritance) In fact there’s not a lot of difference between these in fundamental terms, they are all different ways of injecting client code into the module. In a functional language, you only have the first. In an object oriented language, you have all three (the first may be more or less awkward to do depending on how well function variables are implemented). Hopefully this article provides some pointers as to looking again at the way you close your code against the need to change and open it to be adapted and reused, as success in this area can reap great dividends in maintainability and efficiency. The previous article in this series on the Single Responsibility Principle is at . https://hackernoon.com/you-dont-understand-the-single-responsibility-principle-abfdd005b137 The next article in this series on the Liskov Substitution Principle is at . https://medium.com/@jim_ej/the-liskov-substitution-principle-and-why-you-might-want-to-enforce-it-6f5bbb05c06d Twitter: @jim_ej

Why the Open Closed Principle is the one you need to know but don’t

Before we go into the refactoring process, let’s first look at the alternatives we already have. We will go through each of them and weigh in their pros and cons. This will help us make a better decision. This is a Part 2 to my earlier Part 1 on PHP Software Architecture series: https://medium.com/@sameernyaupane/php-software-architecture-part-1-mvc-1c7bf042a695 If you have not read it yet, please do. Now if you are done with that first article, let’s move on! :) First of all, you may say, why not HMVC/MVVM etc MVC based alternatives? These variations have been discussed in detail by a very smart guy in PHP community, . So I think it is better to just let you go through that article. You can read the article here: Anthony Ferrara https://blog.ircmaxell.com/2014/11/alternatives-to-mvc.html He makes the point that all of these are just slight variations. That still does not fully solve our problem at hand. Now let’s move on to some pretty interesting alternatives. BDD and TDD: BDD stands for Behaviour Driven Development. And TDD stands for Test Driven Development. These are actually not alternatives, even if they are thrown a lot into conversations these days. TDD is a way to write code, irrespective of the architecture we implement. BDD is a variation of TDD with Behavioral approach to it. So these are not going to help us in implementing an architecture style. Although TDD does help set good standards and forces us to move away from the constraints of MVC as the application grows. We can actually follow TDD with implementing any architecture we want. So they go hand in hand instead of as an alternative. DDD : Another term that we often hear in the PHP community is DDD. DDD stands for Doman Driven Design. It was introduced by in his blue book aka. “Domain-Driven Design: Tackling Complexity in the Heart of Software” which was published in 2003. I had actually given a hard thought to DDD as an alternative. But there are some issues here too. First of all DDD is not by any means an easy undertaking. Eric Evans Let’s look at the terms that we need to be familiar with and know the relationships between the parts. DDD Basic Architecture Overview Wait, we’re not done yet. That was just a simple basic architecture overview. Here is the full picture. DDD Full Architecture Diagram Now we see how hard it is for a beginner to even think about implementing one into a project. Most of us do not have that much of luxury to take time and go slow on projects. Projects often have deadlines and we need to take that into consideration. I also feel that there are too many layers than needed, for a simple jump from a MVC application. 3. Hexagonal Architecture: Hexagonal Architecture was introduced by ( ). Alistair Cockburn http://alistair.cockburn.us/Hexagonal+architecture Hexagonal Architecture The main principle behind the hexagonal architecture is the adapter pattern. Each external service that wants to connect to the main application has to go through the Adapter. Each adapter confirms to an interface. This makes it easy to swap an implementation or service. Hexagonal is a bit easy, since all we do is Adapters. But one thing I did not like is the layer separation. Cockburn says “ The rule to obey is that code pertaining to the ‘’inside’’ part should not leak into the ‘’outside’’ part.” So thus we can see that he is following the well known rule “Program to an interface, not implementation”. I think this is a bit overkill for most of our projects. Most of the time (99.999%) we are never going to swap our framework nor our core libraries. Don’t get me wrong, Adapters are good, but using them religiously with Interfaces are not a necessity. Another thing that I see lacking in this architecture is the use of Adapters for everything. The layer of separation is not clearly defined for domain/business logic. We do not need Adapters for framework classes that we need to use. Because we trust them enough and the extra layer of added complexity is rarely of any use. Another thing worthy of mention is that the author of the red book, aka. “Implementing Domain-driven Design”, talks about Hexagonal Architecture in Chapter 4 of the same book. So we can see that DDD can be combined with Hexagonal Architecture in an application. Now talk about the complexity here. One is already tough to implement, let alone two in the same application. ;) Vaughn Vernon 4. Onion Architecture: Jeffrey Palermo coined the term Onion Architecture in his blog ( ). http://jeffreypalermo.com/blog/the-onion-architecture-part-1/ Onion Architecture The architecture relies on Dependency Inversion between layers of applications. I agree with him somewhat on the importance of Dependency Inversion and the use of Interfaces. But I again think it is overkill to do it for all of the layers. Most of the layers do not need to change or swap for pretty much the whole lifetime of an application. This is somewhat related to Hexagonal Architecture, as Jeffrey himself says “ Alistair Cockburn has written a bit about . Hexagonal architecture and Onion Architecture share the following premise: Externalize infrastructure and write adapter code so that the infrastructure does not become tightly coupled.” Hexagonal architecture 5. Clean Architecture Clean Architecture was introduced by . Uncle Bob I’m a big fan of Uncle Bob. I really like his SOLID principles. The Clean Architecture is not bad either. But one thing that Uncle Bob says “Frameworks are out there to get you. You should not extend frameworks”. This is only suitable if you are worried about the framework. I can confidently say most people actually do not change frameworks for the lifetime of a project. I like his ViewModel pattern, which is basically a Decorator pattern. It makes it easy to separate logic from views, making views as dumb as possible. I use that in my own architecture. He also uses Interfaces to separate things from web. That is a bit overkill for web applications to be honest. But for applications that interact with web, cli and/or desktop that is a good way to do it. This Part 2 also got a bit long with all the alternatives we had. So I’ll call this part done. In the next part we will discuss about a simple architecture that I came up with, that you can follow. It is easy to implement and extend. And it basically just extends MVC to make it easier to get started with. Don’t forget to clap this article! Share if you found it useful and follow for Part 3. Thanks :) Link to Part 3: https://medium.com/@sameernyaupane/php-software-architecture-part-3-extensible-architecture-c3fc4d8f0e02 DDD images taken from : https://dotnetcodr.com/2015/08/06/domain-driven-design-with-web-api-revisited-part-1-introduction/ Hexagonal Architecture image taken from: h ttp://alistair.cockburn.us/Hexagonal+architecture Onion Architecture image taken from: http://jeffreypalermo.com/blog/the-onion-architecture-part-1/ Clean Architecture image taken from: https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html

PHP Software Architecture Part 2: The Alternatives

source There is no shortage of new content. Millions of new blog posts are written every day. It’s important that we stay informed for our career, growth and general awareness. We’re all familiar with Newsletters. Newsletters are mini publications, curated by experts and enthusiasts on a focused topic. I like Newsletters, and it’s how I keep up with topics that matter to me. I’m already subscribed to several high-quality tech, startups focused Newsletters. You can check out my on Nucleus. I have a couple of good engineering sources like Hacker News, Reddit. But I wanted to expand my knowledge beyond that. So, I started digging the web for some engineering focused Newsletters. After, spending 2 hours online, I came across a couple of guides that looked promising. One of them is . This is a good master list but feels overwhelming. profile https://github.com/kilimchoi/engineering-blogs After couple of hours of further digging the web, I had compiled a master list of all tech blogs. About 200+ resources. All that left was going over this list and start validating. My validation metrics include content quality, freshness, and coverage. I thought it will be useful to others. So, I decided to put together a guide on best engineering newsletters/blogs. Take your time to review, and subscribe to those that you like. If you want to keep them organized, don’t miss out on the last part of this article. I hope you find this list useful and it helps you stay informed in your respective industries. Please let me know if you have a favorite that I missed it. Android Newsletters: Android Weekly - Free weekly Android development newsletterandroidweekly.net Android Weekly - Free weekly Android development newsletter _Android Authority Newsletters View all our recent newsletter campaigns Stay up to date on all the latest technology…_www.androidauthority.com Android Authority Newsletters - Android Authority A Handcrafted Weekly #AndroidDev Newsletterwww.androiddevdigest.com #AndroidDev Digest - A Handcrafted Weekly #AndroidDev Newsletter Database Newsletters : _A weekly round-up of database technology news and articles covering new developments, SQL, NoSQL, document databases…_dbweekly.com DB Weekly: A Free, Weekly Email Newsletter _A free, once-weekly e-mail round-up of PostgreSQL news and articles_postgresweekly.com Postgres Weekly: A Free, Weekly Email Newsletter _A free weekly newsletter featuring curated news, articles, new releases, events, tools and libraries, jobs etc related…_www.nosqlweekly.com NoSQL Weekly: A Free, Weekly NoSQL E-mail Newsletter _In this blog post, I'll look at the types of NVMe flash health information you can get from using the NVMe command line…_www.percona.com Percona Database Performance Blog _Signup for the MSSQLTips.com newsletter and get free SQL Server tips delivered to you._www.mssqltips.com Join the MSSQLTips SQL Server Community Javascript Newsletters : _Edit description_adripofjavascript.com Home - A Drip of JavaScript _A free, once-weekly e-mail round-up of Node.js news and articles_nodeweekly.com Node Weekly: A Free, Weekly Email Newsletter _A weekly newsletter for front-end developers with a specific focus on tools._webtoolsweekly.com Web Tools Weekly | A weekly newsletter for front-end developers _A free, once-weekly e-mail round-up of JavaScript news and articles._javascriptweekly.com JavaScript Weekly: A Free, Weekly Email Newsletter _We come across a lot of great articles on creating, testing and maintaining large JavaScript applications. This page is…_superherojs.com Superhero.js _Fullstack React is a weekly newsletter about the React ecosystem with an emphasis on useful libraries, tutorials and…_newsletter.fullstackreact.com Fullstack React _The free, weekly newsletter of the best React.js news, articles, projects, and more - brought to you by React.js…_reactjsnewsletter.com React Newsletter _Free weekly occasional summary of React Native news, articles, issues & pull requests, libraries and apps curated by…_reactnative.cc React Native Newsletter iOS Newsletters : _This is a quick look at the changes I needed to make to bring Cocoa with Love up to date for Swift 3 and the latest iOS…_www.cocoawithlove.com Cocoa with Love _In this screencast, you'll learn about classes in C# and how C# manages the memory for them. In this screencast, you'll…_www.raywenderlich.com Tutorials _objc.io publishes books on advanced techniques and practices for iOS and OS X development_www.objc.io objc.io _Subscribe to a hand-picked round up of the best iOS development links every week. Curated by Dave Verwer and published…_iosdevweekly.com iOS Dev Weekly - The best iOS development links, every Friday _Tips and techniques for iOS and Mac development - Weekday mornings at 9:42 AM. The goal of each of these 'bites' is to…_littlebitesofcocoa.com Little Bites of Cocoa - Tips and techniques for iOS and Mac development - Weekday mornings at 9:42… _The greatest iOS development tools, including websites, desktop and mobile apps, and back-end services. Updated daily…_iosdev.tools iOS Dev Tools - The Greatest iOS Development Tools _NSHipster is a journal of the overlooked bits in Objective-C, Swift, and Cocoa. Updated weekly._nshipster.com NSHipster _Hi there, I'm @NatashaTheRobot and I'm programmed to love #Swift! Every week, I put together a list of the best Swift…_swiftnews.curated.co This Week in Swift Company Engineering Blogs: A Language agnostic blogs sharing their latest ideas, and best practices. engineering learnings _All Posts - 8th Light's blog is a place for software crafters to indulge their curiosities, share new ideas, and debate…_8thlight.com All Posts | 8th Light _Welcome to the 500px Engineering Blog! This is where we, the engineers at 500px, share and discuss the challenges and…_developers.500px.com 500px Engineering Blog _Edit description_nerds.airbnb.com Airbnb Engineering - Nerds _Making things work_engineering.bloomreach.com BloomReach Engineering Blog _Introduction Location-specific feedback has always been fundamental to collaboration. At Dropbox, we've recognized this…_blogs.dropbox.com Dropbox Tech Blog _In April of 2016 Etsy launched Pattern, a new product that gives Etsy sellers the ability to create their own hosted e…_codeascraft.com Code as Craft _Meet the engineers who code Facebook_code.facebook.com Engineering Blog _The Blog of the GitHub Engineering Team_githubengineering.com GitHub Engineering _At Heroku, we're always working towards improving operational stability with the services we offer. As we recently…_engineering.heroku.com Heroku Engineering Blog _Stories from the people who build @Instagram_engineering.instagram.com Instagram Engineering _Read more about tech-at-instacart. Instacart Engineering._tech.instacart.com About Tech at Instacart _Stories from Lyft Engineering._eng.lyft.com Lyft Engineering _Join our engineers where we talk about solutions to problems presented by big data and the race for big speed._eng.localytics.com LocalyticsEng _Stories from the team who are building Medium._medium.engineering Medium Engineering _This is a Netflix blog focused on technology and technology issues. We'll share our perspectives, decisions and…_techblog.netflix.com The Netflix Tech Blog _Video publishing at The Times is growing For the past 10 years, the video publishing lifecycle at The New York Times…_open.blogs.nytimes.com Code - Open Blog - The New York Times _Engineers build Quora from the ground up, creating APIs and abstractions to solve challenging technical problems. This…_engineering.quora.com Engineering at Quora _This is part two of a three part series on how we created a technical career path for individuals at Spotify and what…_labs.spotify.com Labs _At Squarespace, our mission is to provide creative tools that help anyone bring their ideas to life. In this blog you…_engineering.squarespace.com Home _Follow the Stripe blog for product announcements, feature updates, new countries, and technical posts about payments._stripe.com Stripe Blog _In the last infrastructure blog post we focused on some of the key efficiency and optimization efforts that we've made…_blog.twitter.com Engineering | Twitter Blogs _The Official Blog_blog.twitch.tv Twitch Blog _The work behind Uber Engineering._eng.uber.com Uber Engineering Blog That’s all! Did I miss any awesome newsletter? Let me know. Found this post useful? Kindly tap the ❤ button below! :) This list was originally curated on . You can checkout from Joel. Sign up to curate the best of what you’re reading for yourself or share with who and what matters to you. Nucleus more engineering curations Editor’s Note: Also check out Hacker Noon Letters :-)

Engineering Newsletters that You Should Subscribe To

Iakov Levin is the CEO of Midas.Investment, a custodial CeDefi investment platform offering yields on cryptocurrency like Bitcoin. Iakov joined us in this AMA to talk about investment in web3 and what his plans are for the future of investment in this new digital era. Slogging This Slogging thread by Jack Boreham, james Burrows, Trevor Midas, Melissa Brown, Lara, Char736, Jimmy L, Cryptodragon, Mónica Freitas, Limarc Ambalina, Sara Pinto, Kelley Dane, Cris Silva, Mark Finnigan, John T., Sonic3625 and Jack swift occurred in slogging's official #amas channel, and has been edited for readability. Jack Boreham Aug 22, 2022, 6:02 PM Hi @channel; it's a pleasure to welcome our next guest, Iakov Levin (Trevor Midas), the CEO and founder of Midas.Investment Midas.Investment is a custodial CeDeFi investment platform offering market-leading yields on BTC, ETH, USDC, and other cryptocurrencies. Midas' mission is to bridge CeFi with the transparency of DeFi. You can ask him anything about: 1) What is Midas? What is the fundamental difference between competitors of other crypto investment custodial platforms? 2) What statistics can the Midas platform share? 3) Why did the MIDAS token perform better than the market and grow by 50% during the crypto winter? 4) What are CeDeFi strategies, and why are they so important to the market at this stage? 5) What are the next key plans for the development of the project? Jack Boreham Aug 22, 2022, 6:03 PM Hi Trevor Midas great to have you with us! Can you start by giving a brief background about yourself and your current work? Trevor Midas Aug 22, 2022, 6:07 PM Hi! Thank you for having me. I am the founder and CEO of Midas.Investments for more than 4 years. My CEO role is fully entwines my crypto path. I have some deep expertise in cognitive science, product management, start-ups and DeFi My previous experience was related to building start-ups and helping others to grow, and then Midas was born, which was a great teacher during those years of challenging crypto markets james Burrows Aug 22, 2022, 6:04 PM Curious to understand what Midas is Trevor Midas Trevor Midas Aug 22, 2022, 6:09 PM Midas.Investments is the CeDeFi platform that offers a vast variety of investment products with the highest APRs on the market. Midas is 4 years old, and we have pivoted multiple times until we have stumbled upon the CeFi yield model back in September of 2021, after which we have started the exponential growth in terms of AUM and userbase. Currently offering 6.5% APR on BTC, 7.8% APR on ETH and 11.6% APR on Stable coins. APR can be boosted by 25% if user picks rewards in Midas token. Our main sources of yield was DeFi, which allowed us to provide really sweat interest rates for users. In the past 8 months we have invested a lot of resources into the creation of our inner asset management, which focuses on DeFi and algorithmic additions on-top. We have created risk frameworks and infrastructure to reduce most of the risk in DeFi protocols, which allowed us to dodge UST and stETH. After building a secure layer on top of the yield process and making it transparent through investment reports, we have started to experiment with CeDeFi strategies, which is our vision for the wealth management of the future. CeDeFi strategies combine simplicity of CeFi, expertise of asset managements and transparency of DeFi. And now we are trying to execute this CeDeFi vision and provide every user the accessible way to build wealth on DeFi. Melissa Brown Aug 22, 2022, 6:08 PM How has your previous experiences helped with developing your platform Trevor Midas? Trevor Midas Aug 22, 2022, 6:12 PM The combination of expertises in product management, human needs and methodologies of solving problems through default brain system really helped me to create the crypto products that are needed by the market. That is why we have pivoted 5 times until we have reached a nice product market fit Lara Aug 22, 2022, 6:10 PM What is CeDiFi? What problem does it solve? Trevor Midas Aug 22, 2022, 6:16 PM We have started to think about CeDeFi concept back in January of 2022, when we were exponentially growing as the CeFi platform. I have always thought about CeFi models, like Celsius and Nexo, as the black box systems, which main goal was to maximise profits while minimizing interest rate to users. It creates the unknown risks for the end-users, like we have seen in June events with Celsius bankrupcy. Therefore, we have started to think about the next step, and it seemed natural that the answer should lie between CeFi and DeFi. CeFi has simplicity and more users; DeFi has transparency and a lot of blocks to build your portfolio from. So, CeDeFi is the answer to the current issues with CeFi lenders that crypto community has suffered from during the last 3 months with the close of Celsius, Voyager, Hodlnaut and others. The CeDeFi strategies looks like basic blocks for your portfolio that can be monitored onchain instead of CeFi black box. There are a Soft long and Soft short on ETH (basically a liquidity pool position, where impermanent loss earns money when ETH is going up (in long) or down (in short), and you get 15-30% APR on top) and DeFi token farming, which gives a nice APR on Convex pools. More strategies are coming in the next couple of weeks to add more variety to yield mechanics. Our main idea is to disrupt the current CeFi models with the efficient and transparent investment blocks that users can build their portfolio from and have fun in the process. I see no future in CeFi until it embraces DeFi market. Char736 Aug 22, 2022, 6:11 PM What growth numbers have you seen? What number do you want to reach in terms of user acquisition? Trevor Midas Aug 22, 2022, 6:19 PM Currently, Midas has $280 mil under management, which was an amazing rally since September, when we had $25 million dollars with the higher crypto marketcap. 9.6k active users on the platform that doubled in the last year. Midas has 50 employees all over the world with 20 employees in investment department (20 employees one year ago). Our main target in the next few months is to validate the market need of CeDeFi strategies. After the launch in three days we got $4 mil in deposits in the three released strategies and almost 1k users trying it, which was a great relief. Our next goal is to target for $50 mil AUM in CeDeFi strategies, which will show that users beside our current user-base need this product. Jimmy L Aug 22, 2022, 6:20 PM Trevor Midas What do you think has been the main reason for such growth? Trevor Midas Aug 22, 2022, 6:25 PM We have built extensive amount of features on the platform, like exchange, lock-in mechanics, dozens of staking and masternode coins, trading algorithms and so on. But the main product for investors was always interest rates. That's why in the previous year we have dropped 10 different features and left only the interest rate coins, while starting to pivoting towards asset management, instead of IT platform. Basically, it helped users to make choice to deposit to Midas. We made the churn much easier and started to position ourselves as CeFi platform. Listed on many monitoring websites, which attracted a lot of attention in a short period of time. Cryptodragon Aug 22, 2022, 6:29 PM What is the difference between Midas and other competitive platforms? Trevor Midas Aug 23, 2022, 2:54 PM The main differences between us and other CeFi platforms are: Transparency on every yield source and how it directs to interest rates The highest rates possible on the market and adaptable with the market. So, if market appreciates yield higher, then it is reflected in our interest rates The CeDeFi strategies fully transparent and with up to 40% yield Trevor Midas Aug 23, 2022, 2:55 PM We are combining our asset management expertise into building our own investment products on top of crypto. The only way we collaborate is with DeFi protocols in order to form a partnership that leads to increased liquidity in DeFi protocol, while giving users a nice exposure to DeFi opportunities 🔥 1 Mónica Freitas Aug 22, 2022, 7:37 PM Hi Trevor Midas. Love the Midas name for an investment platform. It gives a whole second meaning to it. Do you have a selected portfolio of possible investments or do you collaborate with other platforms to have the widest range of ventures? Limarc Ambalina Aug 23, 2022, 7:42 AM Hey thanks again for joining us here on Slogging! My question is: do we need CeDeFi as a term? Once you add aspects of centralized finance, isn't it just centralized finance? Basically I'm questioning whether or not it is possible to even have the best of both worlds. Either a big company can freeze my assets or they can't. Trevor Midas Aug 23, 2022, 2:58 PM Limarc, great question. Yes, you are right in the terms that any CeFi platform has an opportunity to freeze assets. My take on CeDeFi is the possibility of combining transparent wealth sources with the CeFi way for users. DeFi is still a scary and unknown territory for many crypto users. And I see our goal is to make it more accessible to everyone, while keeping the main spirit of DeFi by fully disclosing the address of the strategy. Sara Pinto Aug 23, 2022, 9:48 AM Hey Trevor Midas, great to have you here with us. Can you tell us a bit more about Midas.Investments token? Trevor Midas Aug 23, 2022, 3:14 PM Hey, Sara. The Midas token is a utility token of Midas. It is heavily integrated into Midas platform. Each Midas product contributes to the health and growth of the token and its liquidity. You can earn more yield with Midas token and stake it. If you pick to earn yield in Midas, we are using your initial yield to buy Midas from the market or increase liquidity. It generates up to $1.5m monthly towards the token. Kelley Dane Aug 23, 2022, 11:09 AM Hi Trevor Midas, what statistics can the Midas platform share? Trevor Midas Aug 23, 2022, 4:02 PM Kelley, currently we are showing all the yield statistics, change of your portfolio and assets. Also the allocation for each product and total AUM Cris Silva Aug 23, 2022, 12:51 PM Hello Trevor Midas! Great to meet you! What are your thought on the bear market and how it'll evolve and affect crypto investments? Trevor Midas Aug 23, 2022, 4:03 PM Cris, the bear market is always the build market. I expect a lot of innovation to appear during this two years. New lending services, new DeFi exchanges, new structured products, options, better liquidity, better NFT marketplaces. Maybe even the first fun game with crypto. So, looking forward to it. Additionally, bearish market perishes every non-efficient players from the market, like evolution. Mark Finnigan Aug 23, 2022, 12:52 PM Nice to meet you Trevor Midas. I'm curious about the Midas token. What drove you to create one, and what has it meant for Midas as a company? Trevor Midas Aug 23, 2022, 4:06 PM Mark, token is a great addition to any crypto company, since it allows you to play with so many interesting ideas and concepts, plus it binds the community together. Creation of the token allowed us to gather amazing amount of supporters and the features we have created on top of Midas token helped us survive the hard times of the market John T. Aug 23, 2022, 12:56 PM Hi Trevor Midas, how are you? CeFi and DeFi have started partnering up, but we'll probably need more integration of DeFi in traditional finance systems. What's your best bet on what this integration will look like in the future? Trevor Midas Aug 23, 2022, 4:10 PM John, DeFi is so much more efficient than TradFi in terms of resource management. The great thing about DeFi is interoperability, which allows to build products on top of other products. I feel that in the next ten years DeFi can disrupt TradFi, because it is more efficient to create DeFi protocols than build and use TradFi software. Mónica Freitas Aug 23, 2022, 4:50 PM Trevor Midas understood. What projects in your portfolio are you most proud of? Trevor Midas Aug 24, 2022, 1:06 PM Monica, the most interesting one is Convex, I suppose. It is the governance protocol for managing liquidity on the Curve exchange (more than 1 billion worth of assets). As a holder of Convex you are deciding the way liquidity transfers to various pools and receive bribes from other projects to vote for their pools. Jack Boreham Aug 23, 2022, 4:54 PM Trevor Midas, how will you utilize interoperability with your platfltm? Trevor Midas Aug 24, 2022, 1:07 PM Jack, the CeDeFi layer on top of DeFi allows us to benefit from every innovation that is happening in DeFi, and build our own protocols from those blocks if needed. I feel that this is the safest way to build a reliable business in the volatile crypto - just to be above the market Cris Silva Aug 23, 2022, 5:06 PM Trevor Midas, oh that's interesting. Everyone seems to be treating the bear market as a treat, not as an opportunity. What's left for the NFT market to be better? Does it need more creators and users or just a better integration? Trevor Midas Aug 24, 2022, 1:09 PM Cris, for NFT market there is a huge problem with liquidity. The project that will find the way to efficiently solve the problem of NFT liquidity will bring a lot of new players to the market. I think that just released sudoswap nft exchange has some chances to become this type of platform. Mark Finnigan Aug 23, 2022, 5:21 PM Trevor Midas, a token is definitely a plus for the community.  How long has your token been up for and what's the adoption been like? John T. Aug 23, 2022, 5:10 PM So, do you think that TradFi will become obsolete? I find it hard to believe it'll completely disappear, at least in the upcoming years, as so many people (especially older generations) are not prepared to deal with DeFi, and maybe they're not even interested in learning about it. From your experience, is there something the community and existing companies in the space can do to foster growth and trust in crypto and web investments? Trevor Midas Trevor Midas Aug 24, 2022, 1:31 PM John, I do not think it will completely disappear. There is almost zero liquidity in DeFi for now, and it will take many years until it will become interesting to move from TradFi to DeFi. But the tools are already in the process of development. The only thing that pushes crypto forward is the new innovations. Usually it is solving the next step problem out of time per one cycle. Than this new innovation gets a lot of new variants due to forks, gets a lot of attention and then establishes like a basic level. Then the hype is getting destroyed and crypto clears itself for the entrance of new innovations. 🔥 1 Mark Finnigan Aug 23, 2022, 5:23 PM Also, since you're up to date on the latest investment trends, what are the ones that you think are going to change in the next few years? Trevor Midas Trevor Midas Aug 24, 2022, 1:33 PM Mark, our token is 3 years old. We were really niche in our community for all those years, so we did not reach the full adoption that we expect in the next few years. Regarding investment trends, I am really bullish on the DeFi infrastructure and new ways to generate yield by providing value to protocols. Sara Pinto Aug 23, 2022, 6:08 PM You mention the difference in the performance of the token compared to the market and its growth. How did your token excelled in this? Trevor Midas Trevor Midas Aug 24, 2022, 1:33 PM Sara, Midas token has a huge underlining and capital inflow from our main business activity, which allowed us to be not so correlated with the rest of the market. Kelley Dane Aug 23, 2022, 6:15 PM Trevor Midas, thanks! That seems pretty cool. I just checked your website, and I'm a newbie in all this. So, how does one get started with Midas? Trevor Midas Aug 24, 2022, 1:34 PM Kelley, just log in on the platform, pass KYC and deposit any crypto you want from the list. And that's it. It should take 5-10 mins. Sonic3625 Aug 24, 2022, 11:36 AM What are your long term goals for midas? Trevor Midas Aug 24, 2022, 1:37 PM Sonic, I really wish Midas to become one of the key financial platforms not only in crypto, but in all Fintech. Cris Silva Aug 24, 2022, 1:39 PM Trevor Midas, that's a great point. NFTs quickly devalue as they're sold, except for a few phenomena. Why do you think this happens? Trevor Midas Aug 24, 2022, 3:56 PM Cris, because the price of nft is not backed up by the real liquidity, which makes those assets highly volatile Mark Finnigan Aug 24, 2022, 1:45 PM Trevor Midas so it's a young project. It's still impressive to witness how much it grew in that period. What are the next steps for Midas? Mark Finnigan Aug 24, 2022, 1:45 PM DeFi will certainly see a lot of innovation and work in the upcoming years Trevor Midas Aug 24, 2022, 3:57 PM Mark, the next steps are releasing more strategies and update the token to Ethereum chain to fully sustain the CeDeFi vision Mónica Freitas Aug 24, 2022, 1:47 PM Does Convex work with a liquidity margin? And then adjust to the desired percentage? Trevor Midas Trevor Midas Aug 24, 2022, 3:57 PM Monica, no, its just assets that provided to specific liquidity pools John T. Aug 24, 2022, 1:48 PM Trevor Midas, what have the key factors been for Midas' fast growth? Trevor Midas Aug 24, 2022, 3:57 PM John, I think our work with the community, transparency and the highest yields on crypto Jack swift Aug 24, 2022, 2:08 PM Trevor Midas, who are your main competitors, and what tactics will you employ to remain ahead of them? Trevor Midas Aug 24, 2022, 3:58 PM Jack, our main competitors got bankrupt because of the investing in low liquid assets, so currently we are beneath the ones that left on the empty market Jack Boreham Aug 25, 2022, 10:06 AM And that's a wrap on this AMA Trevor Midas. Thank you so much for joining us. And final thkights, how can people check out Midas Investments? Trevor Midas Aug 26, 2022, 9:04 AM Jack Boreham Thank you for having me! Visit Midas.Investments and join our amazing http://discord.gg/midas Trevor Midas Aug 26, 2022, 9:04 AM Looking forward to see you all

Stories, News & Mentions about 8THLIGHT

8thlight’s Stories on HackerNoon