Nexustorageis in the Enterprise Storage Industry

Nexustorage

nexustorage

The wait is over! - it’s time to celebrate the champion startups of the world. Shout out to all of the participants in our ! You did a wonderful job showcasing your incredible startups and powering through another year. 2023 Startups of the Year is a community-driven voting platform brought to you by HackerNoon that recognizes and celebrates tech startups changing technology and the world for the better. The award started on May 8th, 2023, where the internet nominated and voted for 30k startups around the world. The voting period remained open until December 31, 2023, and now we are here with the winner announcement after a comprehensive evaluation by the HackerNoon team. Startups of the Year 2023 To see the top 3 startups in each respective city, visit and pick a city. hackernoon.com/startups You’ll get a little surprise 😉 Here are the Startups of the Year Regional Announcements: North America Europe Asia Africa South America Oceania Misc/Remote From all of us at HackerNoon, thank YOU for your excellent campaign perseverance 🥺 This year has been awesome! Startups of the Year 2023 is concluded with 623k+ total votes, up from 215k+ votes in the inaugural startup competition. We look forward to seeing you again in the next campaign (stay tuned 😉)! Without further ado, let us kick off the announcement by celebrating the cities with top votes per region for 2023 🎉 North America (11,697 votes): Winner: Bloomfilter Cleveland, Ohio (8,835 votes) - Winner: SerpApi Austin, Texas , California (5,564 votes) - Winner: Finch San Francisco (4,258 votes) - Winner: RELAYTO SoMa, California - (3339 votes) Winner: Windscribe Toronto, Canada, North America (3304 votes) - Winner: Vouched Seattle (2716 votes) - Winner: Seccuri Palo Alto, CA, North America (2671 votes) - Winner: Salsa Valley Miami, FL, North America (2,613 votes) - Winner: Majhi Group Manhattan, New York (2423 votes) - Winner: Flieber, Inc. New York City, NY, North America See the complete announcement for the . Startups of the Year, North America, here Europe (45,612 votes) - Winner: Algomo London, UK (2,344votes) - Winner: Data Lake Warsaw, Poland (1,955 votes) - Winner: Hoken Tech Bari, Italy (1716 votes) - Winner: Not8 Amsterdam, Netherlands (1657 votes) - Winner: KYVE Frankfurt Am Main, Germany (1566 votes) - Winner: BazaIT Kyiv, Ukraine (1496 votes) - Winner:  Unity Network Tallinn, Estonia (1,478 votes) - Winner: Volcaino Ghent, Belgium (1,288 votes) - Winner: Owl Me Dublin, Ireland (1198 votes) - Winner: Groover Paris, France See the complete announcement for the . Startups of the Year, Europe, here Oceania (3,350 votes) - Winner: Sharepass Melbourne (2,107 votes) - Winner: The Catfisher Project Perth, Australia (220 votes) - Winner: Gemini AI Solutions Auckland, New Zealand, Oceania (213 votes) - Winner: Nexustorage Wellington, New Zealand, Oceania (138 votes) - Winner: Coviu Sydney (124 votes) - Winner: Bopple Brisbane, Australia, Oceania (124 votes) - Winner: Regional CFO New South Wales, Australia, Oceania (106 votes) - Winner: Edit on the Spot Gold Coast, Australia, Oceania (93 votes) - Winner: Knowledge Satnav Canbera, Australia, Oceania , Australia, Oceania (48 votes) - Winner: Peptalk360 North Melbourne, Melbourne See the complete announcement for the . Startups of the Year, Oceania, here Asia (16,345 votes) - Winner: Serenity Shield Singapore (13,588 votes) - Winners: QUIXY Telangana, India (10,168 votes) - Winner: HealthySure Mumbai, India (3,865 votes) - Winner: InterviewBuddy Visakhapatnam, India (3,733 votes) - Winner: Omniflo Bengaluru, India (4589 votes) - Winner: MeNow Tel Aviv (3877 votes) - Winner: ForestVPN Dubai (2478 votes) - Winner: TechGraph Powai, Mumbai, India (1004 votes) - Winner: Reelo Ahmedabad, GJ, India (875 votes) - Winner: Debt Hunter Hong Kong, China See the complete announcement for the . Startups of the Year, Asia, here Africa (8,179 votes) - Winner: GO PLATFORM Algiers, Algeria (767 votes) - Winner: Tudu Accra, Ghana (415 votes) - Winner: Treford Lagos, Nigeria (265 votes) - Winner: Phalconwise Ogbomosho, Nigeria (157 votes) - Winner: AbuErdan Cairo (151 votes) - Winner: Eazipay Lekki (144 votes) - Winner: KaziConnect Dar es Salaam, Tanzania (101 votes) - Winner: faceATT Gauteng, South Africa (79 votes) - Winner: Dimagi Cape Town (71 votes) - Winner: Sabi Addis Ababa See the complete announcement for the . Startups of the Year, Africa, here South America (376 votes ) - Winner: UpGirl Santiago, Chile (217 votes) - Winner: Klever Sao Paulo, Brazil (191 votes) - Winner: Tributo Simple Buenos Aires, Argentina (127 votes) - Winner: Light-it Montevideo, Uruguay (87 votes) -Winner: Thousand Antioquia, Colombia (108 votes) - Winner: GetLavado Lima (101 votes) - Winner: Cogniflow Medellin (73 votes) - Winner: TPAGA Bogota (73 votes) - Winner: Reliv Quito (47 votes) - WInner: Quantex Cordoba See the complete announcement for the . Startups of the Year, South America, here Misc/Remote: Featured Startups (1500 votes) - Winner: CIC Chain Remote, Earth (1193 votes) - Winner: Reship Colony US Misc (146 Votes) - Winner: Partful UK, Misc (116 votes) - Winner: GoMining British Virgin Islands Misc (283 Votes) - Winner: tomorrowSpace Germany Misc (225 votes) - Winner: Dtravel Cayman Islands See the complete announcement for Misc/Remote startups . here Once again, HUGE CONGRATULATIONS and BIG PROPS to all of the top Startups of each region this year! The whole team at HackerNoon would like to thank you for your perseverance in the campaign, and we look forward to seeing you in the next campaign. About HackerNoon’s Startups Of The Year Startups of The Year is HackerNoon’s Flagship community-driven event celebrating startups that survived and thrived in 2023. 30,000 startups across 4200+ cities and six continents participated this year to be crowned the best startup in their city. Visit our page to learn more. FAQ Companies that blog more get 67% more leads - Jumpstart your company’s blogging journey by purchasing our . Business Blogging Package The 2023 Startups Of The Year is sponsored by: . . The winners get a free .Tech Domain, a HackerNoon NFT, and a Tech Company News Page. TECH Domains

Stand Up for the Champion Startups of the Year! 

বছরের চ্যাম্পিয়ন স্টার্টআপের জন্য দাঁড়ান!

Setzen Sie sich für die Champion-Startups des Jahres ein!

¡Defiende a las startups campeonas del año!

Défendez les startups championnes de l’année !

वर्ष के चैंपियन स्टार्टअप के लिए खड़े रहें!

今年のチャンピオンスタートアップのために立ち上がろう!

올해의 챔피언 스타트업을 위해 일어서세요!

Defenda as startups campeãs do ano!

Встаньте на защиту стартапов-чемпионов года!

Yılın Şampiyon Startup'ları için Ayağa Kalkın!

Hãy ủng hộ các công ty khởi nghiệp vô địch của năm!

为年度冠军初创企业挺身而出！

How To Write Integration Tests in Go Apps

DRY, or Don't Repeat Yourself, is one of the most well-known software development principles. Many engineers will go to great lengths to achieve this laudable goal, so a successful programming language must be designed with this in mind. Interfaces are just one of the tools that programming languages implement to enable code reuse. Although there are countless differences in the way programming languages implement interfaces, they all define a contract for interaction between software components. Differentiating itself from the typical object-oriented implementation, the Go programming language implements interfaces in a way that aims to reduce complexity, encourage composition, and enable flexible use of the types. Implicit Interfaces The most impactful difference between Go’s interfaces and those from object-oriented languages is that Go’s interfaces work by implicit implementation. Rather than requiring a type to explicitly declare that it implements an interface, determines that a type satisfies an interface as long as it implements all of the required method signatures. The different types and the interface they implement are only coupled by the code using them, rather than always being linked together. Go This difference offers a few key benefits: Reduce complexity and coupling by limiting the hierarchical inheritance of interfaces Simplify types that implement multiple interfaces Enables you to add interfaces later on when they become necessary instead of designing entire applications around them Interfaces can be created for types in different packages This last benefit is the most interesting and unique. The ability to define an interface based on external types leads to a few more specific advantages: Client code can define how it will use types rather than relying on library code to tell it how types must be used Create polymorphic relationships with types that you do not own or cannot change, which allows you to use them more flexibly Solve import cycle issues by changing the location of interface definitions Create mocks of imported types to make your code more testable No Inheritance By excluding inheritance, Go reduces the complexity that can occur from a deep hierarchical structure. When programs are designed around a base set of classes or interfaces, any simple changes to those base structures require a significant refactor. The alternative practice of composition leads to reduced complexity and more readable code. Composition relies on splitting up functionality among different types and using them together, instead of re-defining the functionality of types through inheritance. Now you can re-use these individual components elsewhere, add more functionality with new components, and easily refactor or remove existing ones. Instead of being concerned about what type something , your code just needs to know about what that type , and luckily the interface informs it. is can do Use Case: Polymorphism Polymorphism is perhaps the entire reason behind the existence of interfaces. This common practice is one of the most effective and easy-to-use methods of code reuse. Since an interface defines a strict contract for how types are used, these different types can be used interchangeably; this is polymorphism. A very common and useful scenario for this is having a flexible storage backend for your program: use Postgres in production, SQLite when running locally, and mocks when testing (or skip the database mocks, but that's a topic for another day). type StorageClient interface {
    GetValue(id string) (string, error)
}

func NewStorageClient(clientType string) (StorageClient, error) {
    switch clientType {
        case "sqlite":
            return sqlite.NewClient()
        case "postgres":
            return postgres.NewClient()
        default:
            return nil, fmt.Errorf("invalid client type: %s", clientType)
    }
} This implementation allows you to easily use the interface throughout the program without concern for the data storage layer behind it. StorageClient Use Case: Testing and Mocks You can take advantage of the implicit nature of interfaces by defining an interface for the functions you use from an external library. For example, you are assigned a task to implement a function that fetches recent rain data, in inches, from a weather data API. The made-up weather provider publishes Go package called , which provides a struct with various weather-related methods returning data in metric units: weather Client func GetRainInches(since time.Duration, client weather.Client) (float32, error) {
    rainMM, err := client.GetRain(since)
    if err != nil {
        return 0, fmt.Errorf("error getting data from API: %w", err)
    }

    return rainMM / 2.54, nil
} How will you unit test this code? Since Go has implicit interfaces, you can create your interface that just defines the methods that you need from the library. Now, if your function expects this interface instead, you can create your mocks. Since you currently just need the method, this is simple: GetRain type WeatherClient interface {
    GetRain(time.Duration) (float32, error)
}

func GetRainInches(since time.Duration, client WeatherClient) (float32, error) {
    rainMM, err := client.GetRain(since)
    if err != nil {
        return 0, fmt.Errorf("error getting data from API: %w", err)
    }

    return rainMM / 2.54, nil
} Then, your test file might contain a new struct that also implements the interface: type MockWeatherClient struct {
    expectedErr error
    expectedMM  float32
}

func (c MockWeatherClient) GetRain(time.Duration) (float32, error) {
    return c.expectedMM, c.expectedErr
} After this simple refactor, you do not depend on external libraries to provide interfaces that make your code testable! You have the additional side-effect of being one step closer to allowing your program to use different weather APIs generically. Conclusion and Warnings While interfaces in Go were designed with considerations for simplicity and avoiding some of the common pitfalls of object-oriented patterns, there are still some things to be aware of. It may be tempting to define interfaces for everything with the hopes that you can create a more generic and flexible program. Remember that one of the implicit interfaces is that you can easily create a new interface when you need it without making changes to any existing types, so there is no benefit to creating interfaces early in the process. Additionally, since types do not explicitly declare which interfaces they implement, it may be hard to tell which types are being used by your program when you have superfluous interfaces. While there are always tradeoffs and no perfect solutions, I have found Go's version of interfaces to be incredibly flexible, intuitive, and useful. I have been able to create more flexible programs and improve testability all while minimizing complexity. Also published here.

Go Interfaces Are Just Like Magic

When developing Unity games, you will find that there is lots of code you want to share between all of your projects. It is possible to share these through symbolic links in your filesystem or importing them into the project through a custom package. However, why not go one step further and separate these shared scripts out into open source libraries for other people to share. I have created open source Android libraries before, but when it came to doing the same for Unity it was all very new and there was only a small amount of guidance available online. Here I will document the whole process including setting up source control, writing unit tests, setting up continuous integration and building the final package. Before you begin, make sure your Unity editor is setup properly for keeping your project in Git source control. If you haven’t done this yet, then please check out my article below which tell you more. Prepare Your Unity Project For Git Project Structure When you start writing the code for your package, you will find that there isn’t really any form of enforced project structure. A clear project structure that keeps things nice and organised is usually the best way to go, which is especially important if other people need to read through your code. If you are interested in how I go about structuring my projects, then please check out my article below. A Project Structure for Your Open Source Unity Packages Writing the Code When it comes to the language to write scripts in, I always go with C#. It seems to be the most common in other Unity projects I have looked at and its similarities to Java (and other Object-Oriented languages) make it quite easy to pick up. When it comes to C# classes, it is a really good idea to put all of your classes within your own namespace. This avoids there being name clashes with other classes the user of your package has in their project, much like packages in Java. namespace MyCompanyName.MySuperLibrary {
  
  using SomeOtherNamespace;

  public class MyMainClass {
    ...
  }
} Anyone who wishes to use your class will either reference it with MySuperLibrary.MyMainClass or they can add using MySuperLibrary; to the top of their class. There is an MSDN article to explain how best to name your namespaces. You can see above that the using statements are within the namespace declaration. This ensures that in the case of a class existing in multiple namespaces, the one you intended to use is the one the compiler chooses. Code Documentation There is a trend to focus on writing clean code that is self-documenting instead of relying on comments. However, it is still standard practise for libraries to have documentation on their public API methods. This allows documentation guides to be generated and for IDEs to show you how to use a method when you try to call it. It is therefore suggested you do this for any public methods and classes within your package. <a href="https://medium.com/media/14d8459402116111eb3181a29c20a7f2/href">https://medium.com/media/14d8459402116111eb3181a29c20a7f2/href</a> Most C# IDEs will have a keyboard shortcut to add the documentation block (or an available plugin can add this functionality). Automated Testing Writing unit tests for your C# code couldn’t be much easier, thanks to the Unity Test Tools built right into the editor. For each class you want to test (which is all of them of course), simply create a class with the same name but with the suffix Test in your test sources directory. A common practice is to also add a test suffix to the namespace for the test classes. To match my project structure I therefore add the suffix .UnitTests. The tests themselves are written using standard with the [Test], [SetUp] and [TearDown] attributes, along with the NUnit assertions. NUnit, <a href="https://medium.com/media/43813edbaee05184eb8dbfde4d9a59af/href">https://medium.com/media/43813edbaee05184eb8dbfde4d9a59af/href</a> To run the unit tests, just switch to the Unity editor and open the test runner at Window -> Editor Tests Runner. Feel free to attach the floating window, to make it easier to come back and run the tests again. In this window, you have access to Run All, Run Selected and Rerun Failed. When you run the tests you will see which ones, if any, have failed and if there is a failed test there will be a trace underneath to help you get them all passing. Continuous Integration Now that you have code written for your library and some tests checking that it works, the next step is to get your continuous integration setup. In the case of a Unity project this will involve creating a few simple scripts, for Travis to execute. Install Unity To begin with you will need to download and install the Unity editor. <a href="https://medium.com/media/549f0dfd343fe9b2156e81f4071d8c20/href">https://medium.com/media/549f0dfd343fe9b2156e81f4071d8c20/href</a> If you need to install support for any additional platforms you can add these at the bottom. For example: install "MacEditorTargetInstaller/UnitySetup-Windows-Support-for-Editor-$VERSION.pkg" To find out the name of any packages you need, simply go to the below URL. For the $PLATFORM, enter osx for the Mac environment. $BASE_URL/$HASH/unity-$VERSION-$PLATFORM.ini

http://netstorage.unity3d.com/unity/649f48bbbf0f/unity-5.4.1f1-osx.ini Build your code The next script you need will be to build the code, the best way to ensure it is all working is by building a player for one of the platforms. <a href="https://medium.com/media/904866bd9006ba1d7500aab3f49455a4/href">https://medium.com/media/904866bd9006ba1d7500aab3f49455a4/href</a> The script detailed above will build the project, output any Unity logs to the console, before finishing with 0 for success and 1 for failure. Export Package The final step will be to export your assets to a Unity package. The script can be used to test the process works as well as to create the package to give to your users. <a href="https://medium.com/media/a2f8bc67f7c667cabd52a50c18e38742/href">https://medium.com/media/a2f8bc67f7c667cabd52a50c18e38742/href</a> Within the exportPackage argument, you can specify as many paths as you would like by specifying each as a separate string argument. In the script above only one path is included in the package. Travis The final piece of the puzzle, is to put together the Travis script using the scripts written above. This sits at the root of the project and should be named .travis.yml. <a href="https://medium.com/media/f4bcb5e020f169b9b115c8bd15111962/href">https://medium.com/media/f4bcb5e020f169b9b115c8bd15111962/href</a> At the top, I have specified that the language is Objective-C. This is just to ensure that the environment is setup for Mac and iOS. The osx_image and rvm can be changed to whichever versions you want to use. Before using any of the scripts written above, chmod is used to ensure they are executable. Once this has happened, the install phase can run, which consists of running the install-unity script. After the editor has been installed, the bulk of the CI job consists of building a player with build and then running all of the editor tests with run-tests. If both of these succeed then it will check the package can be exported correctly. Release One option for releasing your package is through the Unity Asset Store, which will be documented very well by Unity Technologies themselves. Here I am going to offer a simple way to release your packages, so that users can download them and include them into their projects. <a href="https://medium.com/media/4f3ee60b008f495611a51bbefd0e2225/href">https://medium.com/media/4f3ee60b008f495611a51bbefd0e2225/href</a> The script accepts the version name as a command-line argument and will then place a named copy of the package into the release directory. This can then be hosted wherever you wish or could be committed to your master branch. With the package in your repository, you should make sure you tag the commit in which you added it with the version name and then prepare a GitHub release. This will allow people to easily go back to each version of your package and it allows you to tell people about new versions of the package. My first Unity package, PowerPrefs, uses everything discussed above, so if you are interested in seeing it in practice then please check it out. andrewlord1990/unity-powerprefs I hope you have found this useful, please let me know if have ideas for any improvements to the process. Good luck creating your own open source Unity packages!

Writing an Open Source Unity Package

Earlier before iOS 7, UITextView uses the web-kit under the hood to render the input by HTML, when we give attributed text. But for many other customisations for many number of lines and complicated functionality, Core-Text is the option left for developers. is a low level frame work which resides on top of the framework in iOS kernel. In other words, Core-Text is a low level Text-engine that when we use along side the frameworks, gives the fine -grained control over and Core-Text : Core-Text Core-Graphics Core-Graphics/Quartz layout formatting. Text-Kit : With iOS 7, Apple released a high level library called Text-Kit, Which is one layer above the Core-Text, and interacts with core text behind the hoods. So developers can avail of this new library(Text-Kit) APIs, for customising the layouts and formats in their App designs. It inherits all the main functionalities of core text and wraps them into objects to provide the needed APIs for the developers. In the need of modifying text details, such as font or layout attributes, one had to deal with , a powerful framework, yet hard to work with. Things became better with , where views could also display rich text, images etc. Core Text attributed strings UITextView TextKit gives us, Rich Text Editing Formatting and syntax highlighting Custom-Layout User Interaction Annotations, Text Effects, Custom Input Behaviour, Text Highlighting, Interaction with UI, etc. → TextKit in iOS handles 3 types of text-attributes. They are Character Attributes These include traits such as Font, colour, subscript which can be associated with an individual character or range of characters. Paragraph Attributes These include Indentation, tabs , line-spacing, etc. These affect the way the Layout Manager arranges lines of text into paragraphs on page. These all are encapsulated into a separate class called NSParagraphStyle Document Attributes These include document traits such as paper-size, margins, view-zooming, etc. → Each in a block of text has a dictionary of , [NSAttributedStringKey.Type: Any] associated with it. character keys and values → Text Kit is composed by three primary classes: The Text Storage class (NSTextStorage) The Layout Manager class (NSLayoutManager) The Text Container class (NSTextContainer) It is a sub class of Class, with the role of storing all the text related information (NSTextAttributedString) such as fonts, paragraph styles, text colours, sizes etc. Its role is also to make sure that all the edited-text-attributed data to be consistent throughout the management and editing sessions. NSTextStorage : NSMutabbleAttributedString As it name implies, this class role is to manage the Text data display on a view object. It takes text data(such as attributed data) from NSTextStorage object, to render the same editing/changes on the view. It gets notified by NSTextStorage object, whenever the changes made to Text-attributes, so every change immediately gets reflected in the Text-input-Views. NSLayoutManager : It handles and support any View object that can be displayed text in it, and perform operations to render unicode characters clearly on views. Note: Strings/ string characters are available in many forms such as ASCII, Unicode, etc. NSLayoutManager object(iOS) supports all unicode characters, So when you encode/decode strings with unicode characters, (such as utf8, utf16) we get some value, so we can safely force unwrap the results. It specifies the views, where the text to be drawn. It manages and handles the view object frames and bounds to specify the text drawing area. It also keep the information of UIBezierPaths (paths) in form of an array, in order to define the text drawing areas from excluding the non text related objects such as images. This way we can show the images and other not text related objects in the text container, with out overlapping with text. NSTextContainer : → → . Note : Except UIWebView, which works with Web-kit frame work, all other remaining Text input fields/views such as UITextView, UITextField, and UILabel objects work with Text-Kit Core-Text Core-Graphics In Text Kit, an _NSTextStorage_ object stores the text that is displayed by a _UITextView_ object and laid out by an _NSLayoutManager_ object into an area defined by _NSTextContainer_ object. And here is the relationship between them. Note: In typography, a glyph is an elemental symbol within an agreed set of symbols, intended to represent a readable character for the purposes of writing.Learn more about Glyphs here In simple words, Glyph is The visual representation of a character that you see. Other Notes: it is sufficient to apply paragraph style to the first character of a paragraph. Text’s vertical position will be configured by independently and separating by using TextView’s properties. If range is == 0, means inserting text else selected or replacing text → All the above mentioned classes have a lot of useful methods to work with RichTextFormat, and further we can extend or sub-class them to configure more. We can subclass the TextStorage, TextContainer, TextAttachment, NSAttributedStrings, NSLayoutManager, etc. UITextVIew can be initialised programatically with custom TextStorage, LayoutManager and TextContainer objects. — — — — — — — — — *********************** — — — — — — — — — If you like my tutorials please follow me on & accounts. , medium twitter linkedIn Thanks for reading… ****************************! !**************************** See you

Stories, News & Mentions about NEXUSTORAGE

Nexustorage’s Stories on HackerNoon