Pantheon is the WebOps platform for websites that deliver extraordinary results. We believe in putting the magic of the internet in everyone’s hands. That’s why we’re so passionate about helping developers, IT, and marketing develop, test, and release website changes faster and more reliably so they can build and maintain websites that create value for their organizations. Our cloud native software makes it easy to securely manage a single website or thousands of websites across multiple teams in one platform. Last year we announced $100 million in Series E funding from SoftBank Vision Fund 2, at a valuation over $1 billion. We are also backed by $100M of venture investment from Sageview Capital (Avalara, Demandbase), Scale Venture Partners (ExactTarget, Box, DocuSign, Bill.com), Foundry Group (SendGrid, Mapbox), as well as Baseline Ventures, First Round Capital, and Floodgate. Follow us to see how Pantheon is powering the open web, running sites in the cloud for customers including Stitch Fix, Okta, Home Depot, Pernod Ricard, and The Barack Obama Foundation. We’re proud to provide the speed and agility web teams need to win in the dynamic world of digital marketing.

Pantheon Platform

Over the past year, we’ve seen a lot of interest from clients in regards to Enterprise blockchain platforms or DLT technologies. Due to privacy, regulation and scalability concerns, businesses tend to go for Private permissioned ledgers instead of using the public mainnet networks that are available currently. As a result, we are seeing two projects that are gaining traction – Enterprise Ethereum and Hyperledger Fabric. In this article, we are going to explore and compare them. Enterprise Ethereum Enterprise Ethereum is the private, consortium implementation of the Ethereum codebase. It is mainly driven by the and its main goals are to address Enterprise requirements, strive for interoperability while evolving around the public Ethereum Blockchain. Enterprise Ethereum Alliance Community Enterprise Ethereum is benefiting from the world’s biggest blockchain developer community. Hundreds of thousands of software engineers, product developers and designers are working in the ecosystem, building the infrastructure, development tools and applications. Deployment Numerous organisations and governments have reported that they are deploying Enterprise Ethereum into their workflow. [1] Hyperledger Fabric , part of the Hyperledger Greenhouse, is the enterprise-grade distributed ledger technology with privacy support, allowing a vast amount of functionality to be plug-and-play (consensus algorithms, components, membership services, etc.). Due to its modularity and versatile design, this technology satisfies a vast amount of use cases regarding businesses and industries (supply chains, healthcare). Hyperledger Fabric Community The Fabric community is steadily increasing, having more than 20 000 users in their , . chat issue tracking, and roadmap Deployment Due to its unique approach regarding DLT, enabling large scale solutions, HLF is intended to be used mainly by enterprises. Clients Let’s explore the different software clients that are available for running Enterprise DLTs. On the EVM based networks, we have the and . , on the other hand, has only one implementation. It does not have clients similar to the EVM based chains. When we are referring to HLF client we will be referring to its only implementation driven by the Linux Foundation. Hyperledger Besu Quorum Hyperledger Fabric Hyperledger Besu Just to make things clear, Hyperledger by itself is an umbrella project under the Linux Foundation. Hyperledger has a set of open-source blockchain projects and development tools. One of the blockchain projects is the Hyperledger Fabric, another one is the Hyperledger Besu (which is the Enterprise Ethereum client, previously developed by ConsenSys with the name of Pantheon). Hyperledger Besu is a client written in Java for EVM-based chains with additional “enterprise-friendly” features. Quorum Quorum is an EVM-based client developed mainly by JP Morgan. It is a fork from the Geth client (written in Go). It was the first enterprise-focused Ethereum client with it’s enhanced privacy features. Enterprise Blockchain Platforms Comparison We can see that both Quorum and Besu have very similar specs, of course, they are both Enterprise Ethereum clients, however, we can mention the following: Besu has a more advanced JSON RPC API permissioning. The client supports JWT authentication, which can be used to define the access rights of the bearer in terms of which RPC can be called etc. With its recent release (1.4.2) the team has added even more tenant-based features. [ ]Quorum has a more advanced on-chain permissioning. We can define organisations, sub organisations, admins, etc using their pre-defined API Calls and contracts. [ ] 4 5 Who provides BaaS? As space matures, we are seeing more and more Cloud Providers offering BaaS solutions. The biggest ones of course are: – AWS currently offers HLF as-a-service and offering Ethereum as-a-service is in their roadmap as-well. – IBM offers HLF as-a-service as-well. – Azure provides deployment of Ethereum (Quorum/Geth) networks along with a Blockchain Development Kit. AWS Managed Blockchain IBM Blockchain Azure Blockchain Other Cloud providers are jumping into the BaaS as-well. At , we are proud to say that we’ve consulted and helped in offering its own Blockchain solutions and enter the market. LimeChain iNNOVO Cloud Future of Enterprise Blockchain Platforms In recent months we are seeing a different approach on how enterprises utilise the technology. Over the last 2-3 years, the main focus of the companies was to produce PoC and figure out how Blockchain can help in their workflows/processes. A lot was learned from those PoCs as Paul Brody (Principal & Global Innovation Leader of Blockchain Technology, at E&Y) mentioned in a recent interview [ ]. There has been a shift in Permissioned Blockchain Networks. It does not seem efficient to deploy blockchain networks for each formed consortium. If we go this way, at some point, companies will be required to join a lot of consortium networks in order to conduct operations with other companies and instead of decreasing the costs using the technology, it would increase the costs because of the complexity. 6 Baseline Protocol Baseline is an released recently that tries to use the public Mainnet (Ethereum) as a common frame of reference. The idea of deploying permissioned networks for consortiums is shifted towards utilising a shared/common infrastructure which is the Mainnet. You can find more information about Baseline Protocol . open-sourced project here The project was in March 2020 and it is supported by Microsoft, E&Y, ConsenSys and many others. announced An important thing to mention is that the Baseline Protocol is used for “state” settlement using a global and shared infrastructure (the Mainnet). The state might be between 2 consortiums (blockchain networks) or it might be between 2 ERPs, it does not matter. Conclusions Enterprise blockchain platforms are becoming more and more mature and ready to be used in production. One or two years ago, developers and administrators had to build their API/on-chain permissioning schemes, but now they are provided as features from the clients themselves. Choosing the right enterprise blockchain platform for your use-case is not a straightforward answer though. The right DLT solution for you is not the same as for others. Hyperledger Fabric networks tend to be preferred by companies that form bigger consortiums. On the other hand, we’ve had use-cases in which HLF network was deployed for internal processes only without any external organisations. The costs for deploying, configuring and maintaining HLF network tend to be higher compared to deploying EVM based network and that’s why we are seeing smaller projects going for Enterprise Ethereum rather than HLF. New protocols are emerging that utilise the public Ethereum Mainnet as a common frame of reference, bringing down the currently siloed Enterprise structures. This provides the ability to avoid problems that come from deploying permissioned networks for consortiums. In the coming months, we will see how this design pattern will play out and whether Enterprises would want to adopt it. We can both on all of the above-mentioned enterprise blockchain platforms. Get in touch with us at consult and develop hi@limechain.tech. USEFUL LINKS [1] - This ConsenSys article provides an extensive list of the governments that use the technology currently [2] - Enterprise Ethereum Client Specification V4 [3] - Onchain permissioning in Hyperledger Besu [4] - Besu JWT Authentication [5] - Quorum Onchain permissioning [6] - Paul Brody Interview [7] - Baseline Protocol Documentation Previously published at https://limechain.tech/blog/enterprise-blockchain-platforms-current-state-and-further-development/

Enterprise Blockchain Platforms: Current State and Further Development

, a leading name in the global crypto sportsbook and casino gaming arena, is thrilled to unveil a groundbreaking collaboration with one of football's most illustrious talents, . WILLEMSTAD, Curaçao, November 29th, 2023/Chainwire/-- Duelbits Luis Suárez This partnership celebrates Suarez's remarkable legacy, including his victories in the Champions League, Copa America, and securing the Golden Boot on two occasions. Luis Suárez, affectionately known as El Pistolero, has left an indelible mark on European football, with storied tenures at Barcelona, Liverpool, Atletico Madrid, and Ajax, and is presently dazzling fans with Gremio in Brazil. A talisman for Uruguay's national team, Suarez has netted over 500 goals, earning him a place among the pantheon of football's greatest strikers. This collaboration signifies a major milestone for Duelbits, as it aligns with a sports figure who embodies the same values of excellence and innovation that have driven Duelbits to the forefront of the industry. As Duelbits continues to foster prestigious partnerships, including with the English Premier League's and , bringing Luis Suárez on board marks another strategic move in expanding its global presence. Aston Villa Argentina's national team Throughout this partnership, Suárez will champion Duelbits' campaigns, lending his image to a brand synonymous with superior quality and unmatched rewards. His professional ethos mirrors Duelbits' commitment to offering a secure, trustworthy, and leading-edge crypto sportsbook and casino experience, further solidifying the brand's identity and its resonance with a discerning global audience. Duelbits is set to amplify this alliance with an enticing welcome offer, providing new members a $100 credit to kickstart their betting journey on any desired outcome upon signing up, thereby inviting fans to not just witness, but also partake in the thrill of the game. In a statement, Luis Suárez shared his excitement about the collaboration, "Joining forces with Duelbits is a proud moment for me. It's more than a partnership; it's a shared vision of excellence and trust. I look forward to what we will achieve together." Marco Pinnisi, CEO of Duelbits, echoed Suarez's sentiments, "We are ecstatic to welcome Luis Suárez to the Duelbits family. His unparalleled achievements and our platform's promise of an exceptional betting experience are a perfect match. We're paving a new path for the future of crypto gambling together." Through this collaboration, Duelbits is poised to continue offering enthusiasts an elevated gaming experience, where innovation and top-tier entertainment converge seamlessly. About Duelbits Duelbits is a leading name in the crypto gaming industry, offering a premium platform tailored for bold and passionate cryptocurrency enthusiasts. With an exclusive library of original games, Duelbits redefines the gaming experience through innovation, personalisation, and unparalleled rewards. The platform prioritises security and trustworthiness, recognising and rewarding every player's unique journey. Our unwavering commitment is to provide the most enriching iGaming experience in the market, defined by fast payments and seamless accessibility. At Duelbits, we pride ourselves on offering the best odds, monumental bonuses, including up to a whopping 50% in Rakeback bonuses, and a uniquely personalised user experience. Positioned at the forefront of embracing cutting-edge innovations, we hold a steadfast belief in advanced technologies, AI, and cryptocurrencies. Each click is a purposeful stride towards an extraordinary adventure. | | | | | Website X Instagram Telegram YouTube d Discor Contact Head of Marketing Caroline Attard caroline.attard@duelbits.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program . here

Duelbits Announces Landmark Collaboration With Football Icon Luis Suárez

Architectural Designs

Unveiling the Nexus: Blockchain in the Context of Contemporary Philosophical Theories

Blockchain in terms of philosophy: From Plato to Foucault

Unchaining the Potential: Exploring Philosophical Implications of Blockchain

A Brief Look At Those Who Laid The Foundation of Blockchain, Decentralization and DeFi

More than two years ago I wrote the following in : my debut Medium article “My desire with [dotNetify] is to get to a state that can support full-stack micro-service on .NET platform: the ability to have a complex web app composable of independent front+back-end modules that can be worked on and deployed by completely autonomous teams with very minimal downtime” I’m delighted to say that with the release of dotNetify version 3.5, this desire has finally been realized! Little did I know then, I was describing something that only a few months before has made the of things to assess. They call it “micro-frontend”, and for better or worse , that term has entered our (software) industry’s pantheon of buzzwords. ThoughtWorks Technology Radar ThoughtWorks elevated the status to “adopt” earlier this year, which I’m glad they did; not just because it makes me feel a bit vindicated, but because we indeed may have found an effective solution to the problem of sprawling front-end monoliths in enterprise applications. But before I continue with this topic, let me quickly cover my obligatory release announcement. What’s New In v3.5 DotNetify is a free, open-source software that helps you build reactive and real-time web application on .NET Core server. It’s unique MVVM approach puts the view models on the back-end and written in C#, and communicate with the UI layer, either written in React, Vue, or Knockout, on web socket through the SignalR technology (but as you will read next, this has become optional in this latest version.) The most significant update in v3.5 is allowing an SPA to communicate with multiple hub servers. Instead of restricting the client-side views to a single, same-origin SignalR hub server, one can create cross-origin hub proxies and use a new lifecycle hook to switch the connection at runtime. Multi-Hubs The above is accomplished by abstracting the part that communicates with the SignalR hub proxy, which incidentally enables high extensibility. The views are no longer coupled to SignalR, and can use different library or protocols to send / receive data. If you don’t really need real-time push, you can now opt for HTTP Web API by including MVC services to , and setting a flag in the connect options: Web API Mode Startup.cs dotnetify.react.connect( , , { : } }); "MyViewModel" this webApi true What the flag does is making your client-side component connect through a hub proxy implementation that communicates to the server as normal HTTP requests to the dotNetify’s built-in Web API endpoint. This endpoint will instantiate the requested view model, set property values if the client sends them, return the serialized JSON in the response body, and dispose the instance. Switching to the Web API mode won’t require too much change to the way you write the C# view models. You just can’t use real-time functions like or multicasting, and you need to keep it stateless; either let the client script manages the state, or always persist the state to a backing store. Any middleware you write will continue to work, except that the hub context argument that’s used to be populated by SignalR hub context will instead get its values from HTTP context. PushUpdates() One other new hub proxy implementation in this release is the local mode. This mode is primarily meant for unit testing, with which you can set up a mock view model to global as illustrated here: Local Mode window .HelloWorld = {
   onConnect() { { : };
   }
}; { (props) { (props); .vm = dotnetify.react.connect( , ); .state = { : };
   } } window return Greetings 'Hello World' . class MyApp extends React Component constructor super this 'HelloWorld' this this Greetings '' /*...*/ Setting an object with the same name as the view model ID to window will allow you to circumvent the server-side connection and make the component gets the state from that object instead. The rest of new version features is detailed in the . I will now go back to discussing the micro-frontend pattern that this version intends to facilitate. v3.5 release notes Micro-Frontend Overview Micro-frontend is an architectural pattern that decomposes an otherwise monolithic web application into decoupled, independently deployable smaller applications. Each one provides a subset of the UI, usually along a bounded context, which will then be stitched together by a light orchestrator to present a single, cohesive front-end to its users. If you think that it sounds more trouble that it’s worth, then most of the time you will be right! Just with microservices, it’s not for everyone. This technique increases both development and deployment complexities, and introduce a whole new set of challenges. So why is this even a ‘thing’? The answer lies on its ability to effectively address the problems with growing, monolithic front-ends in larger organizations. It’s the same set of reasons that compel them to break their back-ends into microservices: It helps them scale their development process across autonomous, geographically-dispersed teams. It reduces deployment risk when they don’t need to deploy everything in one go. It enables faster delivery of new features or bug fixes, when teams don’t have to wait for one another, or run the entire regression test suite. There are many different techniques people have used to implement micro-frontend. The one recommended with dotNetify is closely aligned to the microservices approach, where aspects of functionality is encapsulated within independent web services (or micro-apps), each with its own build process and deployment pipeline. The domain-driven design approach can be employed on deciding how to slice the problem domain into distinct apps. The diagram below depicts the proposed architecture: The entry to the application is provided by what is referred to as a portal service. This service is responsible for performing front-end orchestration, which involves: discovering app services, loading the static UI script bundles dynamically, instantiating and composing their root UI components into a single-page application with client-side routing (which can be done with dotNetify routing system), and redirecting the network traffic to the appropriate service address. The portal service is also responsible for authentication/authorization. It communicates with an identity provider to generate security tokens, and intercept outgoing service requests to inject the tokens into the request header. In production environment, these services should be put behind an API gateway to secure them and have a single entry point into the system. Micro-Frontend Sample Implementation A simple sample implementation covering the application layer of said architecture is provided in the nuget: DotNetify.React.Template dotnet -i dotnetify.react.template
dotnet mfe -o MyApp new new // To run the app, follow the instructions in README.md Executing the command lines above will create a solution consisting of multiple .NET Core projects, representing apps services and a portal service. The UI are mostly developed with React, with one Vue project added into the mix to illustrate the polyglot nature of this solution. Nginx is used for API gateway, and IdentityServer4 for the identity provider. Each app service is an ASP.NET Core web application, configured to build the UI scripts using Webpack when the application is compiled (dev build on , prod build on ). App Services dotnet run dotnet publish The main UI script that serves as the Webpack’s entry point is made to export a function that will return the root UI component as a native Web Component. This will allow the portal service that will load the app’s UI script bundle to create and mount the app’s root component in a framework-agnostic manner. The following is a sample implementation of the main script. The function is provided by dotNetify-Elements to wrap the React component inside an HTML custom element: createWebComponent { createWebComponent } ; MyApp ; elementName = ;
createWebComponent(MyApp, elementName); () => .createElement(elementName); import from 'dotnetify-elements/web-components/core' import from './components/MyApp' const 'my-app-element' export default document The portal service is also an ASP.NET Core web application combined with Webpack. The UI script contains a function called loader which will be executed as soon as the portal starts. This function is given a list containing information on all the app services, including their addresses. For demo purpose, this list is hardcoded. Portal Service loader(
  [
    { : , : , : , : , : },
    ...
  ], [ , ]
); id 'app1' label 'App 1' routePath 'app1' baseUrl '//localhost:8080/app1' moduleUrl '/dist/app.js' // External dependencies required by the apps. 'dotnetify' 'dotNetifyElements' The loader function will ping each app service addresses, and on getting a response, use SystemJS module loader to load the app, and pass the module function that creates the app's root component to an object that manages and displays these components. { appUrl = app.baseUrl + app.moduleUrl; SystemJS.import(appUrl)
    .then( updatePortal({
        ...app, : .default
    }));
} ( ) function importApp app const return => module rootComponent module When the app’s root component is mounted, it will communicate to its own hub server. Since the address is relative, the portal needs to intercept every connect request and redirect it to the correct address. The portal can do this by implementing and use the special identifier that each app will need to provide when its component makes the connect call to forward the request appropriately: dotnetify.connectHandler apps = ;
dotnetify.connectHandler = { appId = vmConnectArgs.options.appId; app = apps.find( x.id === appId); (app) {
    app.hub = app.hub || dotnetify.createHub(app.baseUrl); {
      ...vmConnectArgs, : app.hub, : { 
         ...vmConnectArgs.options, : { : + getAccessToken()}
      }
    };
  }
}; const /* registered apps */ => vmConnectArgs const const => x if return hub options headers Authorization 'Bearer ' Along with the hub change, it too injects the access token to the connect request. The service’s back-end is set up to get the JWT signing keys from IdentityServer4 to authenticate the token. Finally, the portal uses the to dynamically build and run the client-side routing. Any app that use dotNetify routing system will be able to integrate and nest their routes within the portal's root path. NavMenu component from dotNetify-Elements With each micro-frontend app being developed in isolation and deployed independently, naturally there are concerns over visual inconsistencies, and ballooning size due to duplicated dependencies. This can be mitigated by agreeing to use a shared set of core UI components as basic building blocks for the app’s more domain-specific components. Shared UI Library Some organizations have sufficient resources to build their own UI design system, which usually includes a set of themed stylesheets and a common UI component library.  These modules are always referenced by the apps, but can be declared external when bundling.  Only the portal loads them during its initialization so it can be made available to all apps. The reference implementation uses for this common UI library.  This is a set of specialized UI components designed to work with dotNetify view models and fully support reactive programming model.  It's built with React, but it exposes the same components as HTML custom elements, making them reusable in other non-React frameworks. dotNetify-Elements Summary DotNetify v3.5 brings notable enhancements to support micro-frontend pattern to web applications developed with .NET Core back-end, either with SignalR or with standard HTTP Web API. Detailed documentation can be found on . Please direct further questions or feedback to the . Show support for this project with your stars! dotNetify website github issues forum

PANTHEON PLATFORM

pantheon.io

501-1K employees

Since 2010

COMPANY RANKING

PANTHEON PLATFORM

EVERGREEN INDEX #8263

Representing this company? Click here to claim and customize this page!

Pantheon Platform WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

PANTHEON PLATFORM

pantheon.io

501-1K employees

Since 2010

COMPANY RANKING

PANTHEON PLATFORM

EVERGREEN INDEX #8263

RELATED COMPANIESRANK

STORIES ABOUT PANTHEON PLATFORM

Representing this company? Click here to claim and customize this page!

Pantheon Platform WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!